Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: zookeeper-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of timrobertson100@gmail.com
 designates 209.85.215.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=u0/hkKInwEr+WEfgOy44+McPYbXi37igvVerBR8JaKktIcVJYZm5U10EOi0l6VksM7
         /AToAFTTTEYolwvR3XDpmEcX/DQzF3dh0i1KZYQga8nWNjkokUAU/ikVuSjamWY3Xs4O
         WhaAL9pn7YsGTB6Yr1MnWxzHXFeeWQR0ADIAE=
MIME-Version: 1.0
In-Reply-To: <C8B3E6C8.4215A%mahadev@yahoo-inc.com>
References: <AANLkTimhSVAQ4aNPN9UUHh6F1Rd6oPFo2T=FjVwTj=8H@mail.gmail.com>
	<C8B3E6C8.4215A%mahadev@yahoo-inc.com>
Date: Tue, 14 Sep 2010 07:25:06 +0200
Message-ID: <AANLkTi=ytV8caeL5aasvROE-DRcaq=vm+rbViA25J7ww@mail.gmail.com>
Subject: Re: Lock example
From: Tim Robertson <timrobertson100@gmail.com>
To: zookeeper-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Mahadev,

It's good for this confirmation as this is what I ended up doing.


On Mon, Sep 13, 2010 at 11:33 PM, Mahadev Konar <mahadev@yahoo-inc.com> wro=
te:
> Hi Tim,
> =A0The lock recipe you mention is supposed to avoid her affect and preven=
t starvation (though it has bugs :)).
> =A0Are you looking for something like that or just a simple lock and unlo=
ck that doesn't have to worry abt the above issues.
> If that's the case then just doing an ephemeral create and delete should =
give you your lock and unlock recipes.
>
>
> Thanks
> mahadev
>
>
> On 9/8/10 9:58 PM, "Tim Robertson" <timrobertson100@gmail.com> wrote:
>
> Hi all,
>
> I am new to ZK and using the queue and lock examples that come with
> zookeeper but have run into ZOOKEEPER-645 with the lock.
> I have several JVMs each keeping a long running ZK client and the
> first JVM (and hence client) does not respect the locks obtained by
> subsequent clients - e.g. the first client always manages to get the
> lock even if another client holds it.
>
> Before I start digging, I thought I'd ask if anyone has a simple lock
> implemented they might share? =A0My needs are simply to lock a URL to
> indicate that it is being worked on, so that I don't hammer my
> endpoints with multiple clients.
>
> Thanks for any advice,
> Tim
>
>