Github user breed commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/96#discussion_r86678939
--- Diff: src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml ---
@@ -1108,6 +1109,42 @@ server.3=zoo3:2888:3888</programlisting>
</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>reconfigEnabled</term>
+
+ <listitem>
+ <para>(No Java system property)</para>
+
+ <para><emphasis role="bold">New in 3.5.3:</emphasis>
+ This controls the enabling or disabling of
+ <ulink url="zookeeperReconfig.html">
+ Dynamic Reconfiguration</ulink> feature. When the feature
+ is enabled, users can perform reconfigure operations
through
+ the ZooKeeper client API or through ZooKeeper command line
tools
+ assuming users are authorized to perform such operations.
+ When the feature is disabled, no user, including the super
user,
+ can perform a reconfiguration. Any attempt to reconfigure
will return an error.
+ <emphasis role="bold">"reconfigEnabled"</emphasis> option
can be set as
+ <emphasis role="bold">"reconfigEnabled=false"</emphasis> or
+ <emphasis role="bold">"reconfigEnabled=true"</emphasis>
+ to a server's config file, or using QuorumPeerConfig's
+ setReconfigEnabled method. The default value is false.
+
+ If present, the value should be consistent across every
server in
+ the entire ensemble. Setting the value as true on some
servers and false
+ on other servers will cause inconsistent behavior depends
on which server
--- End diff --
depends -> depending
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
