flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Zagrebin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-12380) Add thread name in the log4j.properties
Date Sat, 11 May 2019 16:14:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837888#comment-16837888
] 

Andrey Zagrebin commented on FLINK-12380:
-----------------------------------------

[~yunta] it could be just for historical reasons. As Stephan mentioned, current default log
setting files are already used a lot by users of both logging systems, changing either
format might be unexpected and force users to reconsider logging settings. If somebody wanted
thread name there, they have probably already provided their custom settings.

> Add thread name in the log4j.properties
> ---------------------------------------
>
>                 Key: FLINK-12380
>                 URL: https://issues.apache.org/jira/browse/FLINK-12380
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Yun Tang
>            Assignee: Yun Tang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> This is inspired by FLINK-12368 when users want to add sub-task index information in
the source code. We could add thread name, which already contains sub-task index information,
in the logs to avoid have to change the source code.
> Moreover, I found existing {{logback.xml}} in Flink already contains {{thread name}}
information. We should also add this in the {{log4j.properties.}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message