You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/08/29 07:47:00 UTC

[jira] [Created] (FLINK-10246) Harden and separate MetricQueryService

Till Rohrmann created FLINK-10246:
-------------------------------------

             Summary: Harden and separate MetricQueryService
                 Key: FLINK-10246
                 URL: https://issues.apache.org/jira/browse/FLINK-10246
             Project: Flink
          Issue Type: Improvement
          Components: Distributed Coordination, Metrics
    Affects Versions: 1.6.0, 1.5.3, 1.7.0
            Reporter: Till Rohrmann
             Fix For: 1.6.1, 1.7.0, 1.5.4


This is an umbrella issue to track the effort to harden Flink's {{MetricQueryService}} and to separate it from the rest of the system.

The idea is to setup the {{MetricQueryService}} and the metric system in general in such a way that it cannot interfere with or even bring the main Flink components down. Moreover, the metric system also should not degrade performance by simply using any free CPU cycles but not more. Ideally, the user does not see a difference between running Flink with metric query service turned on or off.



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