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

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/06/11 12:25:00 UTC

[jira] [Updated] (FLINK-8946) TaskManager stop sending metrics after JobManager failover

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

Chesnay Schepler updated FLINK-8946:
------------------------------------
    Affects Version/s: 1.6.0
                       1.5.0

> 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.5.0, 1.4.2, 1.6.0
>            Reporter: Truong Duc Kien
>            Assignee: vinoyang
>            Priority: Critical
>             Fix For: 1.6.0, 1.4.3, 1.5.1
>
>
> 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)