You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Shimin Yang (JIRA)" <ji...@apache.org> on 2018/09/06 06:47:00 UTC

[jira] [Commented] (FLINK-10247) Run MetricQueryService in separate thread pool

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

Shimin Yang commented on FLINK-10247:
-------------------------------------

Hi [~till.rohrmann], do you mean that we should move MetricQueryService out of the Akka Actor System and use a dedicated thread pool to receive the messages and deal with them?

Cheers

> 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
>            Priority: Critical
>             Fix For: 1.6.1, 1.7.0, 1.5.4
>
>
> 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
(v7.6.3#76005)