[
https://issues.apache.org/jira/browse/FLINK-29685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620100#comment-17620100
]
Martijn Visser commented on FLINK-29685:
----------------------------------------
I don't see why this should be added to the ExecutionGraph. The information is
available from logging (which is also where the reason for the failure is sent
to), so why not use it from there?
> 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 JM address for batch jobs after job finished.
> 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)
