flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (Jira)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-14299) Factor status and system metrics out of JobManagerMetricGroup
Date Wed, 02 Oct 2019 16:03:00 GMT

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

Till Rohrmann closed FLINK-14299.
---------------------------------
    Resolution: Done

Done via 972576954e9e3d8d6d6c5e23a6fcad9d60b0a6c8

> Factor status and system metrics out of JobManagerMetricGroup
> -------------------------------------------------------------
>
>                 Key: FLINK-14299
>                 URL: https://issues.apache.org/jira/browse/FLINK-14299
>             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 not only register {{Dispatcher}}
specific metrics but also process specific metrics such as CPU, threads, memory, etc. Due
to this fact, it is not possible to close the {{JobManagerMetricGroup}} when the life time
of the {{Dispatcher}} terminates. In order to do this, I suggest to introduce a new {{ProcessMetricGroup}}
which is used to register the process specific metrics. 
> In order to guarantee backwards compatibility, I suggest to use the same scope format
as {{SCOPE_NAMING_JM}} and then appending {{.Status}}.



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

Mime
View raw message