[
https://issues.apache.org/jira/browse/FLINK-14303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942932#comment-16942932
]
Till Rohrmann edited comment on FLINK-14303 at 10/2/19 4:02 PM:
----------------------------------------------------------------
Done via
7eda4fc0be962d8af5d87c4120a4b5a2a30b9c11
a682254dbdbe4defa3560ec949401622d93a0a83
was (Author: till.rohrmann):
Done via 7eda4fc0be962d8af5d87c4120a4b5a2a30b9c11
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
