You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/01 09:04:00 UTC

[jira] [Updated] (FLINK-14303) Factor resource manager related metrics out of JobManagerMetricGroup

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

ASF GitHub Bot updated FLINK-14303:
-----------------------------------
    Labels: pull-request-available  (was: )

> Factor resource manager related metrics out of JobManagerMetricGroup
> --------------------------------------------------------------------
>
>                 Key: FLINK-14303
>                 URL: https://issues.apache.org/jira/browse/FLINK-14303
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination, Runtime / Metrics
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>
> At the moment, we use the {{JobManagerMetricGroup}} to report resource manager specific metrics such as the number of slots or registered {{TaskExecutors}}. Since the {{JobManagerMetricGroup}} is shared between the {{ResourceManager}} and the {{Dispatcher}} this prevents closing the {{JobManagerMetricGroup}} from the {{Dispatcher}}. 
> In order to solve this problem, I propose to introduce a {{ResourceManagerMetricGroup}} which is used by the {{ResourceManager}} to register resource manager specific metrics. In order to not break existing third party applications which rely on the current metrics layout, the {{ResourceManagerMetricGroup}} will use the scope and group name of the {{JobManagerMetricGroup}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)