[
https://issues.apache.org/jira/browse/FLINK-16620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061363#comment-17061363
]
Jiayi Liao commented on FLINK-16620:
------------------------------------
[~roman_khachatryan] Totally agree with you. This comes to my mind when I was
trying to locate the problem in our production environment and some tasks
restarted several times, which made me have to identify the executions based on
the deploying timestamp in JM when reading logs.
> Add attempt information in logging
> ----------------------------------
>
> Key: FLINK-16620
> URL: https://issues.apache.org/jira/browse/FLINK-16620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Affects Versions: 1.10.0
> Reporter: Jiayi Liao
> Priority: Minor
>
> Currently logging in places such as {{Task}} and {{StreamTask}} , is using
> {{taskNameWithSubtasks}} in {{TaskInfo}} to represent an execution. I think
> it'll be more user-friendly if we can add attempt information into the
> logging.
> The format can be consitent with logging information in {{Execution}} :
> {code:java}
> MySink (3/10) - execution #0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
