Return-Path: Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: (qmail 10191 invoked from network); 25 Feb 2011 23:43:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Feb 2011 23:43:33 -0000 Received: (qmail 32695 invoked by uid 500); 25 Feb 2011 23:43:33 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 32669 invoked by uid 500); 25 Feb 2011 23:43:32 -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 32661 invoked by uid 99); 25 Feb 2011 23:43:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 23:43:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 25 Feb 2011 23:43:30 +0000 Received: (qmail 10097 invoked by uid 99); 25 Feb 2011 23:43:08 -0000 Received: from localhost.apache.org (HELO mail-iw0-f170.google.com) (127.0.0.1) (smtp-auth username phunt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Feb 2011 23:43:08 +0000 Received: by iwn3 with SMTP id 3so1812605iwn.15 for ; Fri, 25 Feb 2011 15:43:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.217.194 with SMTP id hn2mr1470917icb.266.1298677387942; Fri, 25 Feb 2011 15:43:07 -0800 (PST) Received: by 10.42.23.142 with HTTP; Fri, 25 Feb 2011 15:43:07 -0800 (PST) In-Reply-To: References: Date: Fri, 25 Feb 2011 15:43:07 -0800 Message-ID: Subject: Re: Zookeeper for generating sequential IDs From: Patrick Hunt To: user@zookeeper.apache.org Cc: Ertio Lew Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Keep in mind that blog post is pretty old. I see comments like this in the commit log "hard to call it alpha/experimental after serving billions of ids" so it seems it's in production at twitter at least... Patrick On Fri, Feb 25, 2011 at 2:58 PM, Ertio Lew wrote: > Thanks Patrick, > > The fact that it is still in the alpha stage and twitter is not yet > using it, makes me look to other solutions as well, which have a large > community/users base & are more mature. > > I do not know much about the snowflake if it is being used in > production by anyone .. > > > > > On Fri, Feb 25, 2011 at 11:21 PM, Patrick Hunt wrote: >> Have you looked at snowflake? >> >> http://engineering.twitter.com/2010/06/announcing-snowflake.html >> >> Patrick >> >> On Fri, Feb 25, 2011 at 9:43 AM, Ted Dunning wro= te: >>> If your id's don't need to be exactly sequential or if the generation r= ate >>> is less than a few thousand per second, ZK is a fine choice. >>> >>> To get very high generation rates, what is typically done is to allocat= e >>> blocks of id's using ZK and then allocate out of the block locally. =A0= This >>> can cause you to wind up with a slightly swiss-cheesed id space and it = means >>> that the ordering of id's only approximates the time ordering of when t= he >>> id's were assigned. =A0Neither of these is typically a problem. >>> >>> On Fri, Feb 25, 2011 at 1:50 AM, Ertio Lew wrote: >>> >>>> Hi all, >>>> >>>> I am involved in a project where we're building a social application >>>> using Cassandra DB and Java. I am looking for a solution to generate >>>> unique sequential IDs for the content on the application. I have been >>>> suggested by some people to have a look =A0to Zookeeper for this. I >>>> would highly appreciate if anyone can suggest if zookeeper is suitable >>>> for this purpose and any good resources to gain information about >>>> zookeeper. >>>> >>>> Since the application is based on a eventually consistent distributed >>>> platform using Cassandra, we have felt a need to look over to other >>>> solutions instead of building our own using our DB. >>>> >>>> Any kind of comments, suggestions are highly welcomed! :) >>>> >>>> Regards >>>> Ertio Lew. >>>> >>> >> >