Merge pull request #9279 from gyuho/force-new-cluster

Documentation/op-guide: discourage "--force-new-cluster" in recovery
This commit is contained in:
Gyuho Lee 2018-02-26 15:52:42 -08:00 committed by GitHub
commit d6b46ac969
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -61,3 +61,9 @@ $ etcd \
```
Now the restored etcd cluster should be available and serving the keyspace given by the snapshot.
## Restoring a cluster from membership mis-reconfiguration with wrong URLs
Previously, etcd panics on [membership mis-reconfiguration with wrong URLs](https://github.com/coreos/etcd/issues/9173) (v3.2.15 or later returns [error early in client-side](https://github.com/coreos/etcd/pull/9174) before etcd server panic).
Recommended way is restore from [snapshot](#snapshotting-the-keyspace). `--force-new-cluster` can be used to overwrite cluster membership while keeping existing application data, but is strongly discouraged because it will panic if other members from previous cluster are still alive. Make sure to save snapshot periodically.