flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5179) MetricRegistry life-cycle issues with HA
Date Fri, 02 Dec 2016 14:32:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715275#comment-15715275
] 

ASF GitHub Bot commented on FLINK-5179:
---------------------------------------

Github user zentol commented on the issue:

    https://github.com/apache/flink/pull/2886
  
    Actually, i don't know whether @rmetzger did review the functional changes; but that's
only a single line.


> MetricRegistry life-cycle issues with HA
> ----------------------------------------
>
>                 Key: FLINK-5179
>                 URL: https://issues.apache.org/jira/browse/FLINK-5179
>             Project: Flink
>          Issue Type: Bug
>          Components: Metrics
>    Affects Versions: 1.1.3
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Blocker
>             Fix For: 1.2.0, 1.1.4
>
>
> The TaskManager's MetricRegistry is started when the TaskManager is created, and shutdown
in the TaskManager's postStop method.
> However, the registry is also shutdown within the TaskManager's disassociateFromJobManager
method; however it is not restarted when the connection is re-established.
> Effectively this means that a TaskManager that ever reconnected to a JobManager will
not report any metrics, since the reporters are shutdown as well. Metrics will neither be
sent to the WebInterface anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message