You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2022/06/07 03:25:00 UTC
[jira] [Updated] (FLINK-27710) Improve logs to better display Execution
[ https://issues.apache.org/jira/browse/FLINK-27710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu updated FLINK-27710:
----------------------------
Description:
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<}} (graphId: <{{{}short ExecutionGraphID>, vertexId: <{}}}{{{}JobVertexID>{}}}) " and avoid directly display the {{{}ExecutionAttemptID{}}}. This can increase the log readability.
Besides that, the displayed {{JobVertexID}} can also help to distinguish job vertices of the same name, which is common in DataStream jobs (e.g. multiple {{{}Map{}}}).
was:
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{}}} ({{{}short ExecutionGraphID{}}}:{{{}JobVertexID{}}}) ({{{}subtaskIndex+1{}}}/{{{}vertex parallelism{}}}) ({{{}#attemptNumber{}}})" and avoid directly display the {{{}ExecutionAttemptID{}}}. This can increase the log readability.
Besides that, the displayed {{JobVertexID}} can also help to distinguish job vertices of the same name, which is common in DataStream jobs (e.g. multiple {{{}Map{}}}).
> 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
> 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<}} (graphId: <{{{}short ExecutionGraphID>, vertexId: <{}}}{{{}JobVertexID>{}}}) " and avoid directly display the {{{}ExecutionAttemptID{}}}. This can increase the log readability.
> Besides that, the displayed {{JobVertexID}} can also help to distinguish job vertices of the same name, which is common in DataStream jobs (e.g. multiple {{{}Map{}}}).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)