Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F20AD2C9D for ; Tue, 3 May 2011 22:31:42 +0000 (UTC) Received: (qmail 19608 invoked by uid 500); 3 May 2011 22:31:42 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 19586 invoked by uid 500); 3 May 2011 22:31:42 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 19578 invoked by uid 99); 3 May 2011 22:31:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 22:31:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ketan@indeed.com designates 209.85.213.42 as permitted sender) Received: from [209.85.213.42] (HELO mail-yw0-f42.google.com) (209.85.213.42) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 22:31:37 +0000 Received: by ywh1 with SMTP id 1so283325ywh.15 for ; Tue, 03 May 2011 15:31:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.91.201.11 with SMTP id d11mr476941agq.111.1304461876496; Tue, 03 May 2011 15:31:16 -0700 (PDT) Received: by 10.90.70.10 with HTTP; Tue, 3 May 2011 15:31:16 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 May 2011 17:31:16 -0500 Message-ID: Subject: Re: observers in occasionally disconnected data centers From: Ketan Gangatirkar To: user@zookeeper.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks, Mahadev. I had seen ZOOKEEPER-892 but not ZOOKEEPER-784. The latter may be what we need. I read the comments attached to that issue. The most recent comment was a Hudson CI message indicating that the tests against the patch failed. I was not able to find out more as it appears that the configuration of the Apache Hudson has changed. It appears that the patch was approved but not merged into trunk, and it's now in limbo. What is necessary to get that feature into the next release? I may be able to assist, depending on what's involved. Thank you. On Tue, May 3, 2011 at 4:17 PM, Mahadev Konar wrote: > Hi Ketan, > =A0You are correct that observers need connection to quorum as well. > There have been quite a few discussions on multi colo replication and > read only mode of ZooKeeper. > > Here are the jiras for those: > > https://issues.apache.org/jira/browse/ZOOKEEPER-784 > and > https://issues.apache.org/jira/browse/ZOOKEEPER-892 > > These have been mostly targeted at exactly a use case like yours. > Please take a look and them and feel free to contribute/comment on the > jiras. > > -- > thanks > mahadev > @mahadevkonar > > > > On Tue, May 3, 2011 at 2:07 PM, Ketan Gangatirkar wrot= e: >> Hi. =A0We're considering ZooKeeper for coordinating operations across >> multiple data centers. =A0These data centers will occasionally be >> disconnected. =A0We were planning on using observers in remote data >> centers. =A0Our applications can survive being unable to *write* to >> ZooKeeper, but they do need to be able to read from it, even if the >> data were stale. >> >> On further examination, it looks like observers must always be >> connected to the quorum to function at all. =A0Is this correct? =A0Does >> anyone have suggestions for how to work around this problem? =A0The >> first thing that comes to mind is duplicating the required data in >> some other local data store and falling back on that when the DC >> becomes disconnected. =A0I imagine the disadvantages of that are obvious >> to everyone. =A0I hope someone can share some great idea that allows me >> to avoid that miserable fate. =A0Thanks. >> >> -- >> Ketan Gangatirkar >> ketan@indeed.com >> > --=20 Ketan Gangatirkar ketan@indeed.com Perishable Developer