Github user WangTaoTheTonic commented on the issue:
https://github.com/apache/flink/pull/3599
I don't think it's a good idea, as it can not solve the "split brain" issue
too.
The key problem is that `LeaderLatch` in curator is too sensitive to
connection state to Zookeeper(it will revoke leadership when connection to
zookeeper is temporarily broke), and probably the best way is offerring a
"duller" LeaderLatch, which can be also used in standalone cluster.
I did same work in our own private Spark release, let me see if it can be
reused.
---
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.
---
