You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yuxin Tan (Jira)" <ji...@apache.org> on 2023/03/16 08:41:00 UTC

[jira] [Commented] (FLINK-27710) Improve logs to better display Execution

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

Yuxin Tan commented on FLINK-27710:
-----------------------------------

[~zhuzh], I saw you have marked this as "Deprecated at the moment" in the PR, is this finished? If so, Maybe we can close this issue.

> 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, stale-assigned
>
> 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.10#820010)