From 5cd951939d02be528ac3da8066ff5b76334ec498 Mon Sep 17 00:00:00 2001 From: Gyu-Ho Lee Date: Tue, 7 Mar 2017 09:30:41 -0800 Subject: [PATCH] Documentation: warn membership change while migration Fix https://github.com/coreos/etcd/issues/7429. --- Documentation/upgrades/upgrade_3_0.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/upgrades/upgrade_3_0.md b/Documentation/upgrades/upgrade_3_0.md index 085479145d43..eca804e3f0f5 100644 --- 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 < v3.1 does not work properly if built with Go > 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+ & go v1.7+) or (etcd <v3.1 & go v1.6.x). +- Adding a new v3.0 node to v2.3 cluster while migration would trigger panics. 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