Remote replication of Zookeeper data
------------------------------------
Key: ZOOKEEPER-892
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-892
Project: Zookeeper
Issue Type: New Feature
Components: quorum
Affects Versions: 3.4.0
Environment: [r...@llf531123 Zookeeper]# uname -a
Linux llf531123.crawl.yahoo.net 2.6.9-67.0.22.ELsmp #1 SMP Fri Jul 11 10:37:57
EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
[r...@llf531123 Zookeeper]# java -version
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode)
[r...@llf531123 Zookeeper]#
Reporter: Anirban Roy
Assignee: Anirban Roy
Fix For: 3.4.0
ZooKeeper is a highly available and scalable system for distributed synchrony
and is used for cluster management. In its current incarnation it has issues
with cross-colo communication and data replication. Presently, the only way to
distribute ZooKeeper across multiple data centers is to maintain a cross-colo
Quorum using Observer members, leading to huge bandwidth consumption and
performance degradation. The idea behind the ZooKeeper replication feature is
to provide replication of ZooKeeper data from one site to others using a new
type of ZooKeeper member called a Replicator. The Replicator will be
asynchronous, non-intrusive, and can be applied to a subset of the data. It
will be a part of the Main ZooKeeper Site and will push changes to multiple
data centers with guaranteed ordering of events. This 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) data replication with guaranteed ordering, without affecting the Main
ZooKeeper performance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
