The GitHub Actions job "Build documentation" on flink.git has succeeded. Run started by GitHub user zentol (triggered by zentol).
Head commit for run: d745f5b3f7a64445854c735668afa9b72edb3fee / Weijie Guo <res...@163.com> [FLINK-29234] JobMasterServiceLeadershipRunner#closeAsync has a lock with an excessive range 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 narrow the range of lock within JobMasterServiceLeadershipRunner#closeAsync. In the future, we'd better take some measures to avoid possible deadlocks. For example, the leaderEvent of the leaderElectionService is executed by a separate thread. This closes #21137 Report URL: https://github.com/apache/flink/actions/runs/3505679201 With regards, GitHub Actions via GitBox
