From 99e1bd28b88a773841eacce42058a46a5b9c2609 Mon Sep 17 00:00:00 2001 From: Gyuho Lee Date: Mon, 5 Feb 2018 14:07:10 -0800 Subject: [PATCH] Documentation/op-guide: discourage "--force-new-cluster" in recovery Signed-off-by: Gyuho Lee --- Documentation/op-guide/recovery.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/op-guide/recovery.md b/Documentation/op-guide/recovery.md index bb4a9a4ae43..abb34d282bc 100644 --- a/Documentation/op-guide/recovery.md +++ b/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.