Kaynağa Gözat

Documentation/op-guide: discourage "--force-new-cluster" in recovery

Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
Gyuho Lee 8 yıl önce
ebeveyn
işleme
99e1bd28b8
1 değiştirilmiş dosya ile 6 ekleme ve 0 silme
  1. 6 0
      Documentation/op-guide/recovery.md

+ 6 - 0
Documentation/op-guide/recovery.md

@@ -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.