Ben, Ted,
thank you very much for the answers!
On Sat, Jun 7, 2014 at 8:06 AM, Benjamin Reed br...@apache.org wrote:
in the section you are referring to we are pointing out that sometimes you
can reduce the load on ZooKeeper if you avoid waking up the herd when you
don't have to. waking up
in the section you are referring to we are pointing out that sometimes you
can reduce the load on ZooKeeper if you avoid waking up the herd when you
don't have to. waking up 1000 processes so that one of them can become
leader is an unnecessary cost, but if you want everyone to know about a
change
hi,
I am reading the book Zookeeper by Flavio Junqueira and Benjamin Reed.
And I am now concerned if Zookeeper right tool for our scenario:
configuration management. We have ~2000 servers that expected to subscribe
to znode change notification: current version number. As version number
changed all
It is a problem if you expect subsequent watches to go out in milliseconds.
It isn't a problem if the resulting delays are OK with you. To me, it
sounds like it will be just fine. If the herd effect is too much, you can
always split the version flags into many pieces and update one version flag
