Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Wed, 4 May 2011 09:06:03 +0000 (UTC)
From: "Anirban Roy (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: 
 <1991871384.21254.1304499963592.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (ZOOKEEPER-892) Remote replication of Zookeeper
 data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/ZOOKEEPER-892?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anirban Roy updated ZOOKEEPER-892:
----------------------------------

    Attachment:     (was: zoorepl.patch)

> 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: [root@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
> [root@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)
> [root@llf531123 Zookeeper]#=20
>            Reporter: Anirban Roy
>            Assignee: Anirban Roy
>             Fix For: 3.4.0
>
>         Attachments: zoorepl.patch, zoorepl.patch, zoorepl.pdf
>
>   Original Estimate: 2688h
>  Remaining Estimate: 2688h
>
> ZooKeeper is a highly available and scalable system for distributed synch=
rony and is frequently used for cluster management. In its current incarnat=
ion it has issues with communication and data replication across extended g=
eographic locations. Presently, the only way to distribute ZooKeeper across=
 multiple data centers is to maintain a cross-colo Quorum using Observer me=
mbers, leading to unnecessary consumption of bandwidth and performance impa=
cts. As the title suggests, this work aims to to provide replication of Zoo=
Keeper data from one site to others using a new type of ZooKeeper member ca=
lled a Publisher. The broad idea is to have a complete instance of the curr=
ent ZooKeeper at each geographic location in a master-slave setup. The Publ=
isher 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 ZooK=
eeper 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 su=
bset of the data. This scheme will bring about many of the benefits of data=
base replication such as resilience to site failure and localized serving a=
cross data centers. In short, the goal is to provide remote (sub-tree) data=
 replication with guaranteed ordering, without affecting the Master ZooKeep=
er performance.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira