zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jzimmer...@netflix.com>
Subject Re: Use cases for ZooKeeper
Date Thu, 05 Jan 2012 18:02:50 GMT
Curator's queue handles a node going down (when you use setLockPath()).
Curator will hold a lock for each message that is being processed. You can
see the implementation in the method processWithLockSafety() here:

>Will a node going down still clear any distributed locks?


On 1/5/12 9:56 AM, "Josh Stone" <pacesysjosh@gmail.com> wrote:

>Yes, something like that with lock safety would satisfy my third use case.
>Some questions: Is the distributed queue effectively located by a single
>z-node? What happens when that node goes down? Will a node going down
>clear any distributed locks?
>On Thu, Jan 5, 2012 at 9:41 AM, Jordan Zimmerman
>> FYI - Curator has a resilient message Queue:
>> https://github.com/Netflix/curator/wiki/Distributed-Queue
>> On 1/5/12 5:00 AM, "Inder Pall" <inder.pall@gmail.com> wrote:
>> >Third use case: Fault tolerance. If we utilized ZooKeeper to distribute
>> >messages to workers, can it be made to handle a node going down by
>> >re-distributing the work to another node (perhaps messages that are not
>> >ack'ed within a timeout are resent)?

View raw message