reswqa opened a new pull request, #21137:
URL: https://github.com/apache/flink/pull/21137
## What is the purpose of the change
*Currently, in JobMasterServiceLeadershipRunner, Leader event callback such
as grantLeadership and revokeLeadership will be invoked with nested lock(e.g.
curator's event lock and DefaultLeaderElectionService's lock) and try to
acquire JobMasterServiceLeadershipRunner's own lock. This will lead to many
deadlock risks, such as the simultaneous close and grantLeadership. To avoid
this, we should execute this call back in a separate thread to get rid of the
nested structure of locks.*
## Brief change log
- *JobMasterServiceLeadershipRunner handle leader event in a separate
executor to avoid dead lock*
## Verifying this change
This change is covered partially by existing tests and added a new test*.
## 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
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
