lamber-ken opened a new pull request #9158: [FLINK-10052][coordination] 
Tolerate temporarily suspended ZooKeeper connections
URL: https://github.com/apache/flink/pull/9158
 
 
   ## What is the purpose of the change
   ### Desc
   The `ZooKeeperLeaderElectionService` uses the LeaderLatch Curator recipe for 
leader election. The leader latch revokes leadership in case of a suspended 
ZooKeeper connection. This can be premature in case that the system can 
reconnect to ZooKeeper before its session expires. The effect of the lost 
leadership is that all jobs will be canceled and directly restarted after 
regaining the leadership. When more and more tasks deployed in cluster, the 
situation will get worse and worse.
   
   ### Aims
   - Fix the impact of zookeeper network disconnect temporarily on flink long 
running jobs.
   - Improve the stability of the flink longrunning jobs.
   
   
   ## Brief change log
   
     - upgrage curator-recipes dependency to 4.2.0
     - use `SessionConnectionStateErrorPolicy` as the error connect policy when 
build `CuratorFramework`
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as 
*ZooKeeperLeaderElectionITCase*.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes)
     - 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 documented)
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to