zhengzhili333 opened a new pull request, #23866:
URL: https://github.com/apache/flink/pull/23866
## What is the purpose of the change
*Currently, submitting a job starts with storing the JobGraph (in HA setups)
in the JobGraphStore. This includes writing the file to S3 (or some other
remote file system). The job submission is done in the Dispatcher's main
thread. If writing the JobGraph is slow, it would block any other operation on
the Dispatcher.*
## Brief change log
- *The ZooKeeperStateHandleStore create path in ZooKeeper and locks it
then write asynchronously state in Executor*
- *The KubernetesStateHandleStore stores key in ConfigMap and write
asynchronously state in Executor*
- *The dispatcher put JobGraph asynchronously in ioExecutor *
- *The dispatcher write To ExecutionGraphInfoStore asynchronously in
ioExecutor *
## Verifying this change
This change added tests and can be verified as follows:
- *Added the Dispatcher JobSubmission test, use ZooKeeperStateHandleStore
as JobGraphStore*
- *Added the Dispatcher JobSubmission test, use
KubernetesStateHandleStore as JobGraphStore*
## 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, Kubernetes/Yarn, ZooKeeper: (yes)
- The S3 file system connector: (no)
## Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
