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

ASF GitHub Bot commented on FLINK-10247:
----------------------------------------

yanghua commented on a change in pull request #6676: [FLINK-10247][Metrics] Run 
MetricQueryService in separate thread pool
URL: https://github.com/apache/flink/pull/6676#discussion_r216374948
 
 

 ##########
 File path: 
flink-runtime/src/main/java/org/apache/flink/runtime/metrics/dump/MetricQueryService.java
 ##########
 @@ -69,54 +71,24 @@ public String filterCharacters(String input) {
        private final Map<Counter, Tuple2<QueryScopeInfo, String>> counters = 
new HashMap<>();
        private final Map<Histogram, Tuple2<QueryScopeInfo, String>> histograms 
= new HashMap<>();
        private final Map<Meter, Tuple2<QueryScopeInfo, String>> meters = new 
HashMap<>();
+       private ExecutorService threadpool;
 
 Review comment:
   can we mark this field with `final`?

----------------------------------------------------------------
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:
us...@infra.apache.org


> 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.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)

Reply via email to