| commit | 328f985304b07cec046e4b9e4244a9c962fc91f5 | [log] [tgz] |
|---|---|---|
| author | Kezhu Wang <kezhuw@apache.org> | Wed May 31 18:16:59 2023 +0800 |
| committer | GitHub <noreply@github.com> | Wed May 31 18:16:59 2023 +0800 |
| tree | 183786b73fdf712686eda896709a5b9c01603b97 | |
| parent | 4221604facf2447f4ef7789842ac0b8c4a9d4763 [diff] |
CURATOR-671: Make sure success LeaderSelector::requeue after observing hasLeadership and then !hasLeadership (#462) `TestLeaderSelectorCluster.testLostRestart` depends on success `LeaderSelector::requeue` after observing `hasLeadership` and then `!hasLeadership`. #446(CURATOR-518) breaks this. Instead of simply looping till success `LeaderSelector::requeue`, I tend to revert to old behavior as it was that since its introduce in eb4d2aaf7702e7e5ffbf1c1dd8544e88b1171045. Though, we can't depend this in case of no leadership was ever granted. In this case, when session expired, I guess looping on `requeue` may be the only option. Anyway, `requeue` is somewhat hard to use correctly.
Apache Curator is a Java/JVM client library for Apache ZooKeeper, a distributed coordination service.
Apache Curator includes a high-level API framework and utilities to make using Apache ZooKeeper much easier and more reliable. It also includes recipes for common use cases and extensions such as service discovery and a Java 8 asynchronous DSL.
For more details:
