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 Fri, 10 May 2019 09:49:00 GMT

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

Andrey Zagrebin commented on FLINK-12380:

[~yunta] The thread name can be quite long and explode/clutter the log enrtries and size
if we enable it by default in log4j.properties. Users can always do it by themselves if needed
by providing their own log4j.properties and overwriting the default one. What do you think?
If you agree, could you close the issue?

> 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

View raw message