[
https://issues.apache.org/jira/browse/FLINK-29685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623736#comment-17623736
]
LI Mingkun commented on FLINK-29685:
------------------------------------
Logging is also OK. But it is not convenient for users
We also have a log system which provide logs of last 2days.
But data of log is too huge to maintain. So we also archive this logs into a
distribute data system. So we need the JM IPs or container Ids info to search
log from diff JM
> 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)
