Documentation: warn membership change while migration

Fix etcd-io#7429. Signed-off-by: Gyu-Ho Lee <gyuhox@gmail.com>
gyuho · Mar 7, 2017 · 76803ea · 76803ea
1 parent 1a3a345
commit 76803ea
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/Documentation/upgrades/upgrade_3_0.md b/Documentation/upgrades/upgrade_3_0.md
@@ -124,5 +124,6 @@ $ ETCDCTL_API=3 etcdctl endpoint health
 
 - etcd &lt; v3.1 does not work properly if built with Go &gt; v1.7. See [Issue 6951](https://github.com/coreos/etcd/issues/6951) for additional information.
 - If an error such as `transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.` shows up in the etcd server logs, be sure etcd is a pre-built release or built with (etcd v3.1+ &amp; go v1.7+) or (etcd &lt;v3.1 &amp; go v1.6.x).
+- Adding a v3 node to v2.3 cluster during upgrades could trigger panic; see [Issue 7249](https://github.com/coreos/etcd/issues/7429). Mixed versions of etcd members are only allowed during upgrades. Finish the migration before making any membership changes.
 
 [etcd-contact]: https://groups.google.com/forum/#!forum/etcd-dev