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 wrote:
> Hi Tim,
> The lock recipe you mention is supposed to avoid her affect and prevent
> starvation (though it has bugs :)).
> Are you looking for something l
Hi Vishal,
Usually the default retention policy is safe enough for operations.
http://hadoop.apache.org/zookeeper/docs/r3.1.1/zookeeperAdmin.html
Gives you an overview of how to use the purging library in zookeeper.
Thanks
mahadev
On 9/8/10 12:01 PM, "Vishal K" wrote:
> Hi All,
>
> Can you
Hi Tim,
The lock recipe you mention is supposed to avoid her affect and prevent
starvation (though it has bugs :)).
Are you looking for something like that or just a simple lock and unlock that
doesn't have to worry abt the above issues.
If that's the case then just doing an ephemeral create an
Hi Todd,
Sorry for my late response. I had marked this email to respond but couldn't
find the time :). Did you figure this out? It mostly looks like that as soon as
you set a watch on /follower, some other node instantly creates another child
of /follower? Could that be the case?
Thanks
mahad
