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-10247) Run MetricQueryService in separate thread pool
Date Mon, 08 Oct 2018 10:30:00 GMT

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

ASF GitHub Bot commented on FLINK-10247:

tillrohrmann commented on issue #6759: [FLINK-10247][Metrics] Run MetricQueryService in a
dedicated actor system
URL: https://github.com/apache/flink/pull/6759#issuecomment-427786350
   Thanks for updating this PR @Clarkkkkk. I'll give it a pass later today. 
   I think we should not instantiate the `ActorSystem` inside of the `MetricRegistry` and
instead pass it in. That way we are flexible where the `QueryMetricServiceActor` is running.
E.g. in other setups it might be acceptable to share an `ActorSystem` with another component.

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 in separate thread pool
> ----------------------------------------------
>                 Key: FLINK-10247
>                 URL: https://issues.apache.org/jira/browse/FLINK-10247
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Metrics
>    Affects Versions: 1.5.3, 1.6.0, 1.7.0
>            Reporter: Till Rohrmann
>            Assignee: Shimin Yang
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.7.0, 1.6.2, 1.5.5
> In order to make the {{MetricQueryService}} run independently of the main Flink components,
it should get its own dedicated thread pool assigned.

This message was sent by Atlassian JIRA

View raw message