## What is the purpose of the change Fail properly with an exception if we cannot remove the JobGraph in ZooKeeperSubmittedJobGraphStore# removeJobGraph. This is necessary in order to notify callers about the unsuccessful attempt.
When stopping the ZooKeeperSubmittedJobGraphStore, it will release all currently held locks such that other instances can remove entries from the store. This is necessary if we don't immediately close the used CuratorFramework/ZooKeeper client. This PR is based on #6678. ## Verifying this change - Added `ZooKeeperSubmittedJobGraphStoreTest#testJobGraphRemovalFailureAndLockRelease` ## 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: (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) [ Full content available at: https://github.com/apache/flink/pull/6686 ] This message was relayed via gitbox.apache.org for [email protected]
