[
https://issues.apache.org/jira/browse/FLINK-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409672#comment-16409672
]
vinoyang commented on FLINK-8946:
---------------------------------
So [~till.rohrmann] what do you think about this issue in TaskManager (non
flip-6) ? If the tm instance register with a new jm leader. It really could not
work. The reason is it was closed when disconnected from the previous JM leader
as I said in the fisrt comment. Shall we fix this issue?
> TaskManager stop sending metrics after JobManager failover
> ----------------------------------------------------------
>
> Key: FLINK-8946
> URL: https://issues.apache.org/jira/browse/FLINK-8946
> Project: Flink
> Issue Type: Bug
> Components: Metrics, TaskManager
> Affects Versions: 1.4.2
> Reporter: Truong Duc Kien
> Assignee: vinoyang
> Priority: Critical
> Fix For: 1.5.0
>
>
> Running in Yarn-standalone mode, when the Job Manager performs a failover,
> all TaskManager that are inherited from the previous JobManager will not send
> metrics to the new JobManager and other registered metric reporters.
>
> A cursory glance reveal that these line of code might be the cause
> [https://github.com/apache/flink/blob/a3478fdfa0f792104123fefbd9bdf01f5029de51/flink-runtime/src/main/scala/org/apache/flink/runtime/taskmanager/TaskManager.scala#L1082-L1086]
> Perhap the TaskManager close its metrics group when disassociating
> JobManager, but not creating a new one on fail-over association ?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
