You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2018/10/16 03:53:00 UTC
[jira] [Commented] (FLINK-10246) Harden and separate
MetricQueryService
[ https://issues.apache.org/jira/browse/FLINK-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651085#comment-16651085 ]
vinoyang commented on FLINK-10246:
----------------------------------
[~till.rohrmann] Now the remaining two tasks of this task already have PRs, I hope we can work hard to merge it into 1.7.
> 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.5.3, 1.6.0, 1.7.0
> Reporter: Till Rohrmann
> Priority: Critical
> Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> 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)