[
https://issues.apache.org/jira/browse/FLINK-29685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638196#comment-17638196
]
Xintong Song commented on FLINK-29685:
--------------------------------------
Agree with [~martijnvisser], I think this should not be added to Flink.
I think there're better ways to manage the logs in your log system rather than
relying on Flink to provide JM IPs. E.g., grouping logs by Yarn application-id
/ application-attempt-id.
Closing this ticket for now. Please reopen if there's other opinions.
> 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)
