• Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.4.0
    • Fix Version/s: 3.6.0
    • Component/s: server
    • Labels:
    • Environment:
    • Release Note:
      ZOOKEEPER-892. Remote replication of ZooKeeper data (Anirban Roy)
    • Tags:
      zkrepl replication zoorepl


      ZooKeeper is a highly available and scalable system for distributed synchrony and is frequently used for cluster management. In its current incarnation it has issues with communication and data replication across extended geographic locations. Presently, the only way to distribute ZooKeeper across multiple data centers is to maintain a cross-colo Quorum using Observer members, leading to unnecessary consumption of bandwidth and performance impacts. As the title suggests, this work aims to to provide replication of ZooKeeper data from one site to others using a new type of ZooKeeper member called a Publisher. The broad idea is to have a complete instance of the current ZooKeeper at each geographic location in a master-slave setup. The Publisher will be a part of the Master ZooKeeper Site and will push changes to a FIFO queue and make it available to any interested client. The slave ZooKeeper runs client application called Replicator which receives and replays the changes to slave instance. Multiple slave Replicators can subscribes to the master Publisher and receive changes with guaranteed ordering. It will be asynchronous, non-intrusive, loosely-coupled and can be applied to a subset of the data. This scheme will bring about many of the benefits of database replication such as resilience to site failure and localized serving across data centers. In short, the goal is to provide remote (sub-tree) data replication with guaranteed ordering, without affecting the Master ZooKeeper performance.

      1. zoorepl.pdf
        548 kB
        Anirban Roy
      2. zoorepl.patch
        176 kB
        Anirban Roy
      3. zoorepl.patch
        176 kB
        Anirban Roy


        No work has yet been logged on this issue.


          • Assignee:
            Anirban Roy
            Anirban Roy
          • Votes:
            2 Vote for this issue
            16 Start watching this issue


            • Due:

              Time Tracking

              Original Estimate - 2,688h
              Remaining Estimate - 2,688h
              Time Spent - Not Specified
              Not Specified