Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Replicated Nodes using Zookeeper #14

apavlo opened this Issue Jan 11, 2012 · 0 comments


None yet
1 participant

apavlo commented Jan 11, 2012

This goal of this project is add replicated node support in H-Store using Zookeeper. This will enable H-Store to store copies of partitions on multiple nodes. Students will familiarize themselves with the various of issues of ensuring transactional consistency in a parallel, shared-nothing database.

  1. The first step will be to integrate the embedded version of Zookeeper into HStoreSite. Students will implement a basic fail-over detection algorithm and then initiate new master elections. Support for adding new nodes into the replica pool will be added but recovery from snapshots will be implemented by another group. The catalogs will need to extended to include replica information, and any changes to the catalogs (due to elections) must be propagated to all nodes through the HStoreCoordinator.
  2. Once the Zookeeper infrastructure is in place, the students will then choose a replication scheme to implement (e.g., active replication). See Comparison of Database Replication Techniques Based on Total Order Broadcast.
  3. (Optional) Add support for "delayed" node replication. One of the replicas for a given node will purposely trail behind the master node by a certain amount of time. This will allow the administrator to recover from that node in case the database is corrupted by a programmer error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment