[
https://issues.apache.org/jira/browse/FLINK-16620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061229#comment-17061229
]
Roman Khachatryan commented on FLINK-16620:
-------------------------------------------
Thanks for the idea [~wind_ljy].
I think there could be two cases when execution attempt could be useful:
# figuring out what happened with a stream (data) during a particular
execution; for that, we should add it for all log messages and then filter
(which is impractical, unless we implement structured logging)
# figuring out what happened with execution X (e.g. why it failed); for that,
we should add it to start/end
WDYT? Do you have a specific scenario/need in mind?
> 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)
