You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2022/11/24 08:44:00 UTC

[jira] [Closed] (FLINK-29685) Add JM info into ExecutionGraph

     [ https://issues.apache.org/jira/browse/FLINK-29685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xintong Song closed FLINK-29685.
--------------------------------
    Resolution: Won't Do

> Add JM info into ExecutionGraph
> -------------------------------
>
>                 Key: FLINK-29685
>                 URL: https://issues.apache.org/jira/browse/FLINK-29685
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Configuration
>            Reporter: LI Mingkun
>            Priority: Major
>              Labels: execution, runtime
>
> h1. Backgroud
> Web UI didn't show all JM info if enable JM HA now.
> h1. Example
> JM will restart after failed if enable [yarn.application-attempts|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#yarn-application-attempts]. We need to track all JM address for batch jobs after job finished or failed.
> h1. Suggestion
> So, I suggest add multi JM info into ExecutionGraph and archive it into ArchivedExecutionGraph when job finished.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)