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

Chesnay Schepler commented on FLINK-7100:
-----------------------------------------

The problem of affecting other parts of the system are addressed in FLINK-7069. 
With this we reduce the problem to 2 metrics being reporter under the same 
name, which is possible in general and every reporter has to be able to handle 
it anyway.

> TaskManager metrics are registered twice
> ----------------------------------------
>
>                 Key: FLINK-7100
>                 URL: https://issues.apache.org/jira/browse/FLINK-7100
>             Project: Flink
>          Issue Type: Bug
>          Components: Local Runtime, Metrics
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Chesnay Schepler
>              Labels: flip-6
>             Fix For: 1.4.0, 1.3.2
>
>
> TaskManager metrics are currently registered twice, once when the TaskManager 
> is started and once when the TaskManager associates with a JobManager.
> Originally the metrics were registered when the TM associates with the JM and 
> unregistered upon disassociation.
> 9e9776f17ed18b12af177e31ab0bc266236f85ef modified the {{TaskManager}} to use 
> the {{TaskManagerServices}}, which when loaded _also_ register the metrics.
> I suggest to remove the registrations that happen upon (dis-)association.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to