flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10253) Run MetricQueryService with lower priority
Date Mon, 15 Oct 2018 08:52:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649906#comment-16649906

ASF GitHub Bot commented on FLINK-10253:

tillrohrmann commented on issue #6839: [FLINK-10253] Run MetricQueryService with lower priority
URL: https://github.com/apache/flink/pull/6839#issuecomment-429760767
   Concerning the configuration option, I'm ok with adding it. This gives more flexibility
even though I wouldn't expect any user to change it.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Run MetricQueryService with lower priority
> ------------------------------------------
>                 Key: FLINK-10253
>                 URL: https://issues.apache.org/jira/browse/FLINK-10253
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Metrics
>    Affects Versions: 1.5.3, 1.6.0, 1.7.0
>            Reporter: Till Rohrmann
>            Assignee: vinoyang
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.7.0, 1.6.2, 1.5.5
> We should run the {{MetricQueryService}} with a lower priority than the main Flink components.
An idea would be to start the underlying threads with a lower priority.

This message was sent by Atlassian JIRA

View raw message