Return-Path: Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: (qmail 37614 invoked from network); 31 Jan 2011 00:56:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Jan 2011 00:56:35 -0000 Received: (qmail 12396 invoked by uid 500); 31 Jan 2011 00:56:35 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 12345 invoked by uid 500); 31 Jan 2011 00:56:34 -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 12334 invoked by uid 99); 31 Jan 2011 00:56:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jan 2011 00:56:34 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [98.139.52.221] (HELO nm24.bullet.mail.ac4.yahoo.com) (98.139.52.221) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 31 Jan 2011 00:56:27 +0000 Received: from [98.139.52.191] by nm24.bullet.mail.ac4.yahoo.com with NNFMP; 31 Jan 2011 00:56:06 -0000 Received: from [98.139.52.169] by tm4.bullet.mail.ac4.yahoo.com with NNFMP; 31 Jan 2011 00:56:06 -0000 Received: from [127.0.0.1] by omp1052.mail.ac4.yahoo.com with NNFMP; 31 Jan 2011 00:56:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 221690.66611.bm@omp1052.mail.ac4.yahoo.com Received: (qmail 78467 invoked by uid 60001); 31 Jan 2011 00:56:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1296435366; bh=kqabpD54p1MUJS2ILqX84jTHSDnM6V6RfpsbT8XgN54=; h=Message-ID:X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Haf+xy/PpRJ2cD6q6vsZOFKO/o9Mn61dlbfvETQ242EkgvUEP4ZT+LynuUL9VjNL14+JCAciYr7SMCh0SCLm2BhlyslvxlL/Ow9OPehnysbVSqX3jNwOcSWQL0KPFQ0vXDVq4x1yKuwL8PdrlNBubJW4/KHD5wchVkBROHccfeA= Message-ID: <28027.78123.qm@web65515.mail.ac4.yahoo.com> X-YMail-OSG: _Pgqs7sVM1kSyG7TfRt1kpPVfhdkAvUJQNb2R4Ad_hGJcTI Vczt.iQYetZnbkLepztnXUjEzBiysLA9rFY.pEv5XWA9j0TwLXZxRvCBwz_2 ueh4fNUwNdCb7txbBNoQPsLIZb3fEggEUHvNr3rjFJuB30T_CczH6ZursMub ag6pKfqMBoCeudK6ag.75HkVuWPigpODyno1Bha4GuKz6mN6j0XG3knyW9k. vJCGqtE14mRIKMfvxhZyMQWgxTbDaXlGigvaAOjV9ePAj.z1l3aCdhWF6N4. 89t.DYBh4KoKrqXiBMjXosA7f9SL.aDyulyWWf.BuPf6M1uTKrALfSTRRZnx J9WIUSlBxDKEkgPd025WAhARxQTHTdQPXcMJrBj4cAKmdk2eUgBOOnPUNbK_ O11J9TBf7IvI- Received: from [68.123.236.97] by web65515.mail.ac4.yahoo.com via HTTP; Sun, 30 Jan 2011 16:56:05 PST X-RocketYMMF: apurtell X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.107.285259 Date: Sun, 30 Jan 2011 16:56:05 -0800 (PST) From: Andrew Purtell Reply-To: apurtell@apache.org Subject: Re: Extracting Zab from Zookeeper To: dev@zookeeper.apache.org Cc: user@zookeeper.apache.org In-Reply-To: <4D430A95.1080000@yahoo-inc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable FWIW, we have this crazy idea of using something like an extracted ZAB for = maintaining quorum-cliques in a modified HBase cluster: https://issues.apac= he.org/jira/browse/HBASE-2357=0A=0A - Andy=0A=0A> From: Benjamin Reed =0A> Subject: Re: Extracting Zab from Zookeeper=0A> To: "= dev@zookeeper.apache.org" =0A> Cc: "Ted Dunning" = , "user@zookeeper.apache.org" =0A> Date: Friday, January 28, 2011, 10:27 AM=0A> flavio and ted are c= orrect. zab and=0A> zookeeper are tightly coupled, and =0A> as flavio point= s out, zab provides a bit more than just=0A> atomic broadcast.=0A> =0A> i t= hink it would be a good thing to do for three reasons:=0A> =0A> 1) it would= make testing, benchmarking, and fixing that layer =0A> (especially for ZOO= KEEPER-22) much easier.=0A> 2) we could try different backends easier. (i'd= love to try=0A> using bookkeeper for example.)=0A> 3) although the zab int= erface must be richer than normal=0A> atomic broadcast (access to past tran= sactions, for example), i=0A> think in practice applications that do primar= y/backup can benefit=0A> from this richer interface.=0A> =0A> ben=0A> =0A> = On 01/28/2011 07:03 AM, Ted Dunning wrote:=0A> > I think that what Flavio w= as saying is that it is like=0A> > pulling a string on a sweater.=A0 Almost= any application that=0A> > wants ZAB is probably going to need the broadca= st and they the=0A> > broadcast, they will want to have logging.=A0 And tra= nsactions.=0A> >=A0 And so on.=0A> >=0A> > Moreover, some of these features= are not necessarily=0A> > encoded in ZK in a way that you can point to.=A0= Instead they are=0A> > enabled by the way that several functional units ar= e glued=0A> > together.=0A=0A=0A=0A