You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2018/09/10 09:02:46 UTC

[GitHub] Clarkkkkk opened a new pull request #6676: [FLINK-10247][Metrics] Run MetricQueryService in separate thread pool

Clarkkkkk opened a new pull request #6676: [FLINK-10247][Metrics] Run MetricQueryService in separate thread pool
URL: https://github.com/apache/flink/pull/6676
 
 
   ## What is the purpose of the change
   
   Introduce a dedicated thread pool for MetricQueryService to process messages.
   
   
   ## Brief change log
     - Add a single executor thread pool for MetricQueryService
     - Wrap the logic of processing message in a Runnable and submit to the thread pool once receiving any message
   
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as *(please describe tests)*.
   
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - Design: Using a Single Executor thread pool to avoid racing condition, messages will still be processed one by one.
   

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


With regards,
Apache Git Services