Apache ZooKeeper 3.4.3 has been released by Patrick Hunt.
From the post:
ZooKeeper 3.4 is incorporated into CDH4 and now available in beta 1!
ZOOKEEPER-1367 is the most serious of the issues addressed, it could cause data corruption on restart. This version also adds support for compiling the client on ARM architectures.
- ZOOKEEPER-1367 Data inconsistencies and unexpired ephemeral nodes after cluster restart
- ZOOKEEPER-1343 getEpochToPropose should check if lastAcceptedEpoch is greater or equal than epoch
- ZOOKEEPER-1373 Hardcoded SASL login context name clashes with Hadoop security configuration override
- ZOOKEEPER-1089 zkServer.sh status does not work due to invalid option of nc
- ZOOKEEPER-973 bind() could fail on Leader because it does not setReuseAddress on its ServerSocket
- ZOOKEEPER-1374 C client multi-threaded test suite fails to compile on ARM architectures.
- ZOOKEEPER-1348 Zookeeper 3.4.2 C client incorrectly reports string version of 3.4.1
If you are running 3.4.2 or earlier, be sure to upgrade immediately. See my earlier post for details on what’s new in 3.4.
From the Apache ZooKeeper homepage:
ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them ,which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.
Just in case you hope to manage distributed applications some day. Zookeeper should be on your resume.