Perhaps something similar to what Ben detailed here? (rendezvous)

Change the key, add child znode(s) that's deleted by the "notified"
client(s) once it's read the changed value. Some details need to be
worked out but seems reasonable.


On Tue, Nov 9, 2010 at 6:42 PM, Ben Hall <> wrote:
> Hi All...
> Long time reader... First time writer...  Hehe...
> I am curious to know what successes people have had with verifying zookeeper 
> changes across a pool of clients.  I.E. Being able to verify that your 
> changed Key did in fact get pushed out to all of the subscribed clients.
> We are looking at creating a hash of the finished key value and comparing 
> that with what is on the ZK server... But curious if anyone has any smarter 
> ideas.
> Thanks
> Ben

Reply via email to