Github user hanm commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/590#discussion_r219660892
--- Diff: zookeeper-docs/src/documentation/content/xdocs/zookeeperAdmin.xml
---
@@ -1025,6 +1025,102 @@ server.3=zoo3:2888:3888</programlisting>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>watchManaggerName</term>
+
+ <listitem>
+ <para>(Java system property only: <emphasis
+
role="bold">zookeeper.watchManaggerName</emphasis>)</para>
+
+ <para><emphasis role="bold">New in 3.6.0:</emphasis> Added in
+ <ulink
url="https://issues.apache.org/jira/browse/ZOOKEEPER-1179";>ZOOKEEPER-1179</ulink>
New watcher
+ manager WatchManagerOptimized is added to optimize the
memory overhead in heavy watch use cases. This
+ config is used define which watch manager to be used.
Currently, we only support WatchManager and
+ WatchManagerOptimized.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>watcherCleanThreadsNum</term>
+
+ <listitem>
+ <para>(Java system property only: <emphasis
+
role="bold">zookeeper.watcherCleanThreadsNum</emphasis>)</para>
+
+ <para><emphasis role="bold">New in 3.6.0:</emphasis> Added in
+ <ulink
url="https://issues.apache.org/jira/browse/ZOOKEEPER-1179";>ZOOKEEPER-1179</ulink>
The new watcher
+ manager WatchManagerOptimized will clean up the dead
watchers lazily, this config is used to decide how
+ many thread is used in the WatcherCleaner. More thread
usually means larger clean up throughput. The
+ default value is 2, which is good enough even for heavy
and continuous session closing/receating cases.</para>
--- End diff --
`closing/recreating`
---
