*Issue 1:*
*Matteo's Response:*
*"The way I understand this is that you might get less notifications than*
*the number of changes on the z-node, but when you set the watch, it
shouldbe tied to the z-node version that you have already read, so you
should beget notified for any change after
On Tue, Mar 7, 2017 at 10:10 AM, Charan Reddy G
wrote:
> Hey,
>
> *Issue 1:*
>
> I was going through the code to understand how BookiesChanged event is
> handled for AuditTask (in Auditor, BookkeeperAdmin and BookieWatcher
> classes). In BookieWatcher.notifyBookiesChanged they are making
> getChi
On Tue, Mar 7, 2017 at 10:10 AM Charan Reddy G
wrote:
> But due to the limitation of ZK (which is well documented thing in ZK
> https://zookeeper.apache.org/doc/r3.4.5/zookeeperProgrammers.html#ch_
> zkWatches), "Because watches are one time triggers and there is latency
> between getting the eve
