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


[ Full content available at: https://github.com/apache/flink/pull/6676 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to