Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 58670 invoked from network); 11 Jan 2010 18:09:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Jan 2010 18:09:02 -0000 Received: (qmail 34436 invoked by uid 500); 11 Jan 2010 18:09:01 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 34374 invoked by uid 500); 11 Jan 2010 18:09:01 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 34355 invoked by uid 99); 11 Jan 2010 18:09:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 18:09:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of adam.rosien@gmail.com designates 209.85.216.204 as permitted sender) Received: from [209.85.216.204] (HELO mail-px0-f204.google.com) (209.85.216.204) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 18:08:51 +0000 Received: by pxi42 with SMTP id 42so15983213pxi.5 for ; Mon, 11 Jan 2010 10:08:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=etGGmO2np7wBTaCzq7yP+Z2aS6tnbaV8PkZwIPAgSs0=; b=agyLHQjiaJsuYHk6m+zizcNXoJskCHGb8HopguTyvmr20S9qySQSv5j/bv5PkcdFqq K4JAeSkihCdLXCZ8smbWl/VgGiUNP1Pg5B/2qMfQgHUek8tbX8j2Ob+PAjxj+s1A+Vdk pAYPEFtEoMM6MEI2Jy4RDpDBbKh5Nw1UW8aRo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=g5n6uW+iGvEeZHsFCb+RNkRlKC9DjKZNNOVEEjXLEYEFdwRlSMJJ44rJmf3qofBzzW 4o7fke0WyyAPy20krGr8fg+gvSW2V8fnb5YDU7aST1NekArxcLop9yrW3WGOtsUsyaiB FVDD74+MuPCFTrqzpiaADnhIrwUC3XfCQDOfo= MIME-Version: 1.0 Sender: adam.rosien@gmail.com Received: by 10.142.247.21 with SMTP id u21mr6250060wfh.233.1263233309751; Mon, 11 Jan 2010 10:08:29 -0800 (PST) In-Reply-To: <4B4B64B3.4000102@apache.org> References: <4B4B64B3.4000102@apache.org> Date: Mon, 11 Jan 2010 10:08:29 -0800 X-Google-Sender-Auth: bc0416f9622e3f51 Message-ID: Subject: Re: blog post about zk and group membership From: Adam Rosien To: zookeeper-user@hadoop.apache.org Cc: "zookeeper-dev@hadoop.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Thanks Patrick. Re "off the shelf", my title of "Actually Implementing" was a *bit* snarky to try and gain some readers, but it wasn't intended to be sharp criticism; more documented recipes is a good thing for everyone. I'd be happy to submit a JIRA with a group membership recipe. Re zkclient, I agree that documentation is a big thing, which I hope to help out with as I use it more. I'm talking now with one of the developers about zkclient's implementation of data serialization since that is another big area; zk pushes all serialization semantics into the clients, which is ok but requires its own practical strategies. .. Adam On Mon, Jan 11, 2010 at 9:49 AM, Patrick Hunt wrote: > Adam, this is awesome! I've retweeted it on my twitter account: > http://twitter.com/phunt/status/7637054275 > > A few comments: > > 1) you are correct about the "off the shelf" part, but really alot of that > is our marketing blurb, we paint with a broad stroke. I think it would make > sense to include this sort of detail in the "recipes" page though, would you > be interested to create a JIRA and submit some content? (you could re > purpose alot of what you have in your post) > > 2) re zkclient - I have not been following that project closely of late, > however Mahadev and I did review their code a few months ago. At that time > we had some concerns about the semantic impact of some of the design choices > they made (which were fine, just not well documented and therefor easy for > users to miss). In particular (again, at the time, may be addressed by now) > watch notifications could be lost during disconnected/expired sessions, and > the user would not be made aware of this. > > 3) excellent point/suggestion on the "rogue" service > > Patrick > > Adam Rosien wrote: >> >> I've written a blog post about using ZooKeeper for group membership at >> KaChing: >> >> http://bit.ly/6yraP6 >> http://eng.kaching.com/2010/01/actually-implementing-group-management.html >> >> Any comments or feedback is welcome. >> >> .. Adam >