ZK is an application programmer's interface to the Apache ZooKeeper server. It is based on the zookeeper gem which is a multi-Ruby low-level driver. Currently MRI 1.8.7, 1.9.2, 1.9.3, REE, and JRuby are supported. Rubinius 2.0.testing is supported-ish (it's expected to work, but upstream is unstable, so YMMV).
ZK is licensed under the MIT license.
The key place to start in the documentation is with ZK::Client::Base (rubydoc.info, local).
See the RELEASES file for information on what changed between versions.
This library is heavily used in a production deployment and is actively developed and maintained.
Development is sponsored by Snapfish and has been generously released to the Open Source community by HPDC, L.P.
ZooKeeper is a multi-purpose tool that is designed to allow you to write code that coordinates many nodes in a cluster. It can be used as a directory service, a configuration database, and can provide cross-cluster locking, leader election, and group membership (to name a few). It presents to the user what looks like a distributed file system, with a few important differences: every node can have children and data, and there is a 1MB limit on data size for any given node. ZooKeeper provides atomic semantics and a simple API for manipulating data in the heirarchy.
One of the most useful aspects of ZooKeeper is the ability to set "watches" on nodes. This allows one to be notified when a node has been deleted, created, changed, or has had its list of child znodes modified. The asynchronous nature of these watches enables you to write code that can react to changes in your environment without polling and busy-waiting.
Znodes can be ephemeral, which means that when the connection that created them goes away, they're automatically cleaned up, and all the clients that were watching them are notified of the deletion. This is an incredibly useful mechanism for providing presence in a cluster ("which of my thingamabobers are up?). If you've ever run across a stale pid file or lock, you can imagine how useful this feature can be.
Znodes can also be created as sequence nodes, which means that beneath a given path, a node can be created with a given prefix and assigned a unique integer. This, along with the ephemeral property, provide the basis for most of the coordination classes such as groups and locks.
ZooKeeper is easy to deploy in a Highly Available configuration, and the clients natively understand the clustering and how to resume a session transparently when one of the cluster nodes goes away.
The zookeeper gem provides a low-level, cross platform library for interfacing with ZooKeeper. While it is full featured, it only handles the basic operations that the driver provides. ZK implements the majority of the recipes in the ZooKeeper documentation, plus a number of other conveniences for a production environment. ZK aims to be to Zookeeper, as Sequel or ActiveRecord is to the MySQL or Postgres drivers (not that ZK is attempting to provide an object persistence system, but rather a higher level API that users can develop applications with).
ZK provides:
- a robust lock implementation (both shared and exclusive locks)
- a leader election implementation with both "leader" and "observer" roles
- a higher-level interface to the ZooKeeper callback/watcher mechanism than the zookeeper gem provides
- a simple threadpool implementation
- a bounded, dynamically-growable (threadsafe) client pool implementation
- a recursive Find class (like the Find module in ruby-core)
- unix-like rm_rf and mkdir_p methods
- an extension for the Mongoid ORM to provide advisory locks on mongodb records
In addition to all of that, I would like to think that the public API the ZK::Client provides is more convenient to use for the common (synchronous) case. For use with EventMachine there is zk-eventmachine which provides a convenient API for writing evented code that uses the ZooKeeper server.
See the RELEASES page for more info on features and bugfixes in each release.
ZK strives to be a complete, correct, and convenient way of interacting with ZooKeeper. There are a few things to be aware of:
-
In versions < 0.9 there is only one event dispatch thread. It is very important that you don't block the event delivery thread. In 1.0, there is one delivery thread by default, but you can adjust the level of concurrency, allowing more control and convenience for building your event-driven app.
-
ZK uses threads. You will have to use synchronization primitives if you want to avoid getting hurt. There are use cases that do not require you to think about this, but as soon as you want to register for events, you're using multiple threads.
-
If you're not familiar with developing solutions with zookeeper, you should read about sessions and watches in the Programmer's Guide. Even if you are familiar, you should probably go read it again.
-
It is very important that you not ignore connection state events if you're using watches.
-
ACLS: HOW DO THEY WORK?! ACL support is mainly faith-based now. I have not had a need for ACLs, and the authors of the upstream twitter/zookeeper code also don't seem to have much experience with them/use for them (purely my opinion, no offense intended). If you are using ACLs and you find bugs or have suggestions, I would much appreciate feedback or examples of how they should work so that support and tests can be added.
-
ZK::Client supports asynchronous calls of all basic methods (get, set, delete, etc.) however these versions are kind of inconvenient to use. For a fully evented stack, try zk-eventmachine, which is designed to be compatible and convenient to use in event-driven code.
- papertrail: Hosted log management service
- redis_failover: Redis client/server failover managment system
- DCell: Distributed ruby objects, built on top of the super cool Celluloid framework.
-
The zookeeper gem (repo).
-
For JRuby, the slyphon-zookeeper_jar gem (repo), which just wraps the upstream zookeeper driver jar in a gem for easy installation
- if you really want to, you can also reach me via twitter @slyphon