Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of rajkumar.w93@gmail.com
 designates 209.85.161.42 as permitted sender)
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:content-type
         :content-transfer-encoding;
        b=iaWrf4IOyga/0so0buMF0sqQ/pYGFKXFKCiP0MUOq3f3srwQrwCQm3jnRwFDq4ZgFv
         1T08mDVSFpCOVfhPhWoyGJ4BKJyDNgT1pEz/VLHTX6WfzLNZl7/SqYmyVUuxWzIbN9GZ
         SPxmTFGxYZxDxgqc8/UP9jnxm30NjspZpcWkE=
MIME-Version: 1.0
Sender: rajkumar.w93@gmail.com
In-Reply-To: <AANLkTikN8SAVvTBZ6aJCOvXaQOgb7uudHfpBv1LZTbke@mail.gmail.com>
References: <AANLkTi=Of77TdUpQQmjbNUzquejFe=zPzENcjwfK885b@mail.gmail.com>
	<AANLkTimNRt=2brNcs0sAJSLY+fMCYBMvTGu8E2QG_Z6i@mail.gmail.com>
	<AANLkTikNP_+qV4_D_oTaDeFuTPmf5ng+r=77a8jbtDXX@mail.gmail.com>
	<AANLkTinyOanus1PLewHfD1=WAUcq9QWvevecUxAmDSY6@mail.gmail.com>
	<AANLkTikN8SAVvTBZ6aJCOvXaQOgb7uudHfpBv1LZTbke@mail.gmail.com>
Date: Mon, 28 Feb 2011 20:30:07 +0530
Message-ID: <AANLkTi=1FUxjJ3Pk_uVYkUxYymcU1cN+S+2gKSdaJiqb@mail.gmail.com>
Subject: Re: Zookeeper for generating sequential IDs
From: Ertio Lew <ertiop93@gmail.com>
To: user@zookeeper.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Patrick,

I considered your suggestion. But sadly it could not fit my use case.
I am looking for a solution that could help me generate 64 bits Ids
but in those 64 bits I would like atleast 4 free bits so that I could
manage with those free bits to distinguish the type of data for a
particular entity in the same columnfamily.

If I could keep the snowflake's Id size to around 60 bits, that would
have been great..


On Sat, Feb 26, 2011 at 5:13 AM, Patrick Hunt <phunt@apache.org> wrote:
> 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 <ertiop93@gmail.com> 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 <phunt@apache.org> 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 <ted.dunning@gmail.com> wr=
ote:
>>>> If your id's don't need to be exactly sequential or if the generation =
rate
>>>> 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 alloca=
te
>>>> blocks of id's using ZK and then allocate out of the block locally. =
=A0This
>>>> 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 =
the
>>>> id's were assigned. =A0Neither of these is typically a problem.
>>>>
>>>> On Fri, Feb 25, 2011 at 1:50 AM, Ertio Lew <ertiop93@gmail.com> 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 suitabl=
e
>>>>> 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.
>>>>>
>>>>
>>>
>>
>