ZOOKEEPER-2865: Reconfig Causes Inconsistent Configuration file among…

… the nodes Author: Alexander Shraer <ashraer@apple.com> Reviewers: Michael Han <hanm@apache.org> Closes #328 from shralex/ZOOKEEPER-2865
apache · Aug 6, 2017 · fe6eac3 · fe6eac3
1 parent 5c4e443
commit fe6eac3
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 0 deletions.
diff --git a/docs/zookeeperReconfig.html b/docs/zookeeperReconfig.html
@@ -855,6 +855,10 @@ <h4>General</h4>
 
 </div>
 </div>
+<p>If the configuration of existing servers changes or they become unavailable
+          before the joiner succeeds to connect and learn obout configuration changes, the
+          joiner may need to be restarted with an updated configuration file in order to be
+          able to connect.</p>
 <p>Finally, note that once connected to the leader, a joiner adopts
           the last committed configuration, in which it is absent (the initial
           config of the joiner is backed up before being rewritten). If the

diff --git a/docs/zookeeperReconfig.pdf b/docs/zookeeperReconfig.pdf
diff --git a/src/docs/src/documentation/content/xdocs/zookeeperReconfig.xml b/src/docs/src/documentation/content/xdocs/zookeeperReconfig.xml
@@ -550,6 +550,10 @@ zk.getConfig(watcher, callback, context);</programlisting>
             independently from your main ensemble. It is OK to list multiple
             joiners as observers in an initial config.</para>
         </note>
+        <para>If the configuration of existing servers changes or they become unavailable
+          before the joiner succeeds to connect and learn obout configuration changes, the
+          joiner may need to be restarted with an updated configuration file in order to be
+          able to connect.</para>
         <para>Finally, note that once connected to the leader, a joiner adopts
           the last committed configuration, in which it is absent (the initial
           config of the joiner is backed up before being rewritten). If the