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)?
>>Third use-case is done by kafka(ZK based consumer) wherein new consumers getting added/removed from group notifies existing consumers(they release all their work) and redistribute the work among themselves. to me second use-case is a leader election/lock use-case. Curator looks good for it as i tried the ZK lock recipe and it has some issues.. I am planning to use it for leader election and some sample code is at - https://github.com/InMobi/data-bus/blob/master/src/main/java/com/inmobi/databus/zookeeper/CuratorLeaderManager.java I am not sure about first use-case. On Thu, Jan 5, 2012 at 2:25 PM, Jordan Zimmerman <[email protected]>wrote: > Care to work on it? > > On 1/5/12 12:50 AM, "Ted Dunning" <[email protected]> wrote: > > >This pattern would make a nice addition to Curator, actually. It comes up > >repeatedly in different contexts. > > -- Thanks, - Inder Tech Platforms @Inmobi Linkedin - http://goo.gl/eR4Ub
