Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
due to this zk bug:
https://issues.apache.org/jira/browse/ZOOKEEPER-706
we can't handling session re-establishment when watcher set size on zk client side goes beyond 1M. we need at least 2 things:
1) add watcher size monitoring mechanism, log warnings when watcher set size goes beyond 1M. this could be done through reflection on zk-connection
2) reduce number of watchers helix needs. one possible solution is to register only one watcher on parent node and every time we change a znode under the parent node, we touch the parent node.