Apache ZooKeeper is a software project of the Apache Software Foundation. It is essentially a service for distributed systems offering a hierarchical key-value store, which is used to provide a distributed configuration service, synchronization service, and naming registry for large distributed systems (see Use cases). ZooKeeper was a sub-project of Hadoop but is now a top-level Apache project in its own right.
|Developer(s)||Apache Software Foundation|
|License||Apache License 2.0|
ZooKeeper's architecture supports high availability through redundant services. The clients can thus ask another ZooKeeper leader if the first fails to answer. ZooKeeper nodes store their data in a hierarchical name space, much like a file system or a tree data structure. Clients can read from and write to the nodes and in this way have a shared configuration service. ZooKeeper can be viewed as an atomic broadcast system, through which updates are totally ordered. The ZooKeeper Atomic Broadcast (ZAB) protocol is the core of the system.
ZooKeeper was originally developed at Yahoo! for streamlining the processes running on big-data clusters by storing the status in local log files on the ZooKeeper servers. These servers communicate with the client machines to provide them the information. ZooKeeper was developed in order to fix the bugs that occurred while deploying distributed big-data applications.
Some of the prime features of Apache ZooKeeper are:
- Reliable System: This system is very reliable as it keeps working even if a node fails.
- Simple Architecture: The architecture of ZooKeeper is quite simple as there is a shared hierarchical namespace which helps coordinating the processes.
- Fast Processing: ZooKeeper is especially fast in "read-dominant" workloads (i.e. workloads in which reads are much more common than writes).
- Scalable: The performance of ZooKeeper can be improved by adding nodes.
Apache ZooKeeper Architecture
Some common terminologies regarding the ZooKeeper architecture:
- Node: The systems installed on the cluster
- ZNode: The nodes where the status is updated by other nodes in cluster
- Client Applications: The tools that interact with the distributed applications
- Server Applications: Allows the client applications to interact using a common interface
The services in the cluster are replicated and stored on a set of servers (called an "ensemble"), each of which maintains an in-memory database containing the entire data tree of state as well as a transaction log and snapshots stored persistently. Multiple client applications can connect to a server, and each client maintains a TCP connection through which it sends requests and heartbeats and receives responses and watch events for monitoring.
Typical use cases for ZooKeeper are:
In addition to the client libraries included with the ZooKeeper distribution, a number of third-party libraries such as Apache Curator and Kazoo are available that make using ZooKeeper easier, add additional functionality, additional programming languages, etc.
Apache projects using ZooKeeper
- "Apache ZooKeeper - Releases". Retrieved 13 June 2019.
- "Index - Apache ZooKeeper - Apache Software Foundation". cwiki.apache.org. Retrieved 2016-08-26.
- "Zookeeper Overview".
- "ZooKeeper/Powered By". Archived from the original on 2013-12-09. Retrieved 2012-01-25.
- "Why Reddit was down on Aug 11".
- "5 Big DaaS Challenges and How to Overcome Them | NetApp Newsroom". NetApp Newsroom. 2016-06-20. Retrieved 2017-05-24.
- "Location-Aware Distribution: Configuring servers at scale". Facebook Code. 2018-07-19. Retrieved 2018-07-20.
- "ZooKeeper at Twitter". Twitter Engineering Blog. 2018-10-11. Retrieved 2018-12-08.