Load the zookeeper node data as well as attaching another data watcher, then invoke the applyZKData implementation to process the data string.
Load the zookeeper node data as well as attaching another data watcher, then invoke the applyZKData implementation to process the data string.
Reconnect to the zookeeper, this maybe invoked when zookeeper connection expired and the node data watcher previously registered got dropped, hence re-attache the data wather here.
Reconnect to the zookeeper, this maybe invoked when zookeeper connection expired and the node data watcher previously registered got dropped, hence re-attache the data wather here.
Optional, the destination to report the stats to
Optional, the destination to report the stats to
TODO: pick up new rev of Cluster once it's ready Soon enough the Cluster will be defined in a way that we can directly managing the managers in a more flexible way, by then we should be able to do batch update we want here.
TODO: pick up new rev of Cluster once it's ready Soon enough the Cluster will be defined in a way that we can directly managing the managers in a more flexible way, by then we should be able to do batch update we want here. For now, the updating pool is still done one by one.
zookeeper client talking to the zookeeper, it will only be used to read zookeeper
zookeeper client talking to the zookeeper, it will only be used to read zookeeper
the zookeeper path representing the cache pool
the zookeeper path representing the cache pool
Zookeeper based cache pool cluster with a serverset as the underlying pool. It will monitor the underlying serverset changes and report the detected underlying pool size. It will also monitor the serverset parent node for cache pool config data, cache pool cluster update will be triggered whenever cache config data change event happens.