From 122744c660ae5df9f3e38f03f99c1bc373ffeebc Mon Sep 17 00:00:00 2001 From: Sam Batschelet Date: Wed, 20 Mar 2019 17:03:52 +0000 Subject: [PATCH] Documentation: update force-new-cluster flag usage for v3 Signed-off-by: Sam Batschelet --- Documentation/op-guide/configuration.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/op-guide/configuration.md b/Documentation/op-guide/configuration.md index 3c5db2bf9e6..53b79307826 100644 --- a/Documentation/op-guide/configuration.md +++ b/Documentation/op-guide/configuration.md @@ -359,7 +359,7 @@ For example, it may panic if other members in the cluster are still alive. Follow the instructions when using these flags. ### --force-new-cluster -+ Force to create a new one-member cluster. It commits configuration changes forcing to remove all existing members in the cluster and add itself. It needs to be set to [restore a backup][restore]. ++ Force to create a new one-member cluster. It commits configuration changes forcing to remove all existing members in the cluster and add itself, but is strongly discouraged. Please review the [disaster recovery][recovery] documentation for preferred v3 recovery procedures. + default: false + env variable: ETCD_FORCE_NEW_CLUSTER @@ -428,3 +428,4 @@ Follow the instructions when using these flags. [systemd-intro]: http://freedesktop.org/wiki/Software/systemd/ [tuning]: ../tuning.md#time-parameters [sample-config-file]: ../../etcd.conf.yml.sample +[recovery]: recovery.md#disaster-recovery