[jira] [Updated] (FLINK-9741) Register JVM metrics for each JM separately

["Chesnay Schepler (JIRA)" <ji...@apache.org>]

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

Chesnay Schepler updated FLINK-9741:
------------------------------------
    Fix Version/s:     (was: 1.6.0)
                   1.7.0

> Register JVM metrics for each JM separately
> -------------------------------------------
>
>                 Key: FLINK-9741
>                 URL: https://issues.apache.org/jira/browse/FLINK-9741
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Coordination, Metrics
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.7.0
>
>
> Currently, the {{Dispatcher}} contains a {{JobManagerMetricGroup}} on which the JVM metrics are registered. the JobManagers only receive a {{JobManagerJobMetricGroup}} and don't register the JVM metrics.
> As the dispatcher and jobmanagers currently run in the same jvm, neither exposing their IDs to the metric system, this doesn't cause problem _right now_ as we can't differentiate between them anyway, but it will bite us down the line if either of the above assumptions is broken.
> For example, with the proposed exposure of JM/Dispatcher IDs in FLINK-9543 we would not expose JVM metrics tied to a JM, but only the Dispatcher.
> I propose to register all JVM metrics for each jobmanager separately to future proof the whole thing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)