[
https://issues.apache.org/jira/browse/FLINK-27710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551665#comment-17551665
]
Zhu Zhu commented on FLINK-27710:
---------------------------------
Thanks for the comments. [~xtsong]
I think your concern is valid. I'm also not pretty sure which name pattern
would be the best. I would leave this ticket open for a while and watching in
ML to see if other devs/users complain about the task name in logs after the
execution ID rework.
> Improve logs to better display Execution
> ----------------------------------------
>
> Key: FLINK-27710
> URL: https://issues.apache.org/jira/browse/FLINK-27710
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination, Runtime / Task
> Affects Versions: 1.16.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Currently, an execution is usually represented as "{{{}job vertex name{}}}
> ({{{}subtaskIndex+1{}}}/{{{}vertex parallelism{}}}) ({{{}attemptId{}}})" in
> logs, which may be redundant after this refactoring work. With the change of
> FLINK-17295, the representation of Execution in logs will be redundant. e.g.
> the subtask index is displayed 2 times.
> Therefore, I'm proposing to change the format to be "<{{{}job vertex name>
> {{}}}}(<{{{}subtaskIndex>+1{}}}/<{{{}vertex parallelism>{}}})
> {{#<attemptNumber>}} (graph: <{{{}short ExecutionGraphID>, vertex:
> <{}}}{{{}JobVertexID>{}}}) " and avoid directly display the
> {{{}ExecutionAttemptID{}}}. This can increase the log readability.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
