Github user wenlong88 commented on the issue:
https://github.com/apache/flink/pull/3599
Hi, @WangTaoTheTonic I think we can improve the reaction of
ZookeeperLeaderElectionService on zookeeper connection expired or other errors
instead of introducing the AlwaysLeaderService such as adding a retry before
revoking leadership, because when the problem is caused by errors on the
machine which JM is running on, we need to trigger a failover to make the JM
change a machine.
On the other hand, in the coming FLIP-6 implementation, JM failover will
not trigger cancelling all running tasks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
