Home Explore Help
Register Sign In
publics
/
etcd-io__etcd
0
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Browse Source

Merge pull request #7441 from gyuho/warning

Documentation: warn membership change while migration
Gyu-Ho Lee 8 years ago
parent
1a3a345468 43eca30a08
commit
3f515e1849
1 changed files with 1 additions and 0 deletions
Unified View Show Diff Stats
  1. 1 0
      Documentation/upgrades/upgrade_3_0.md

+ 1 - 0
Documentation/upgrades/upgrade_3_0.md
View File 

@@ -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.
 
 - 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).
 
 - 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 v3 node to v2.3 cluster during upgrades is not supported and could trigger panics. See [Issue 7249](https://github.com/coreos/etcd/issues/7429) for additional information. Mixed versions of etcd members are only allowed during v3 migration. Finish upgrades before making any membership changes.
 
 
 
 [etcd-contact]: https://groups.google.com/forum/#!forum/etcd-dev
 
 [etcd-contact]: https://groups.google.com/forum/#!forum/etcd-dev