From d05d522398882bca8804ef47d4982ef11428aab0 Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Thu, 9 Aug 2018 10:13:27 -0700 Subject: [PATCH] Documentation: v2: add -- for force new cluster this doc is inconsistent between --force-new-cluster and -force-new-cluster. Use the latter as it is the preferred option in etcd. --- Documentation/v2/admin_guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/v2/admin_guide.md b/Documentation/v2/admin_guide.md index 2826a7434..faba828d1 100644 --- a/Documentation/v2/admin_guide.md +++ b/Documentation/v2/admin_guide.md @@ -239,13 +239,13 @@ This command will rewrite some of the metadata contained in the backup (specific #### Restoring a backup -To restore a backup using the procedure created above, start etcd with the `-force-new-cluster` option and pointing to the backup directory. This will initialize a new, single-member cluster with the default advertised peer URLs, but preserve the entire contents of the etcd data store. Continuing from the previous example: +To restore a backup using the procedure created above, start etcd with the `--force-new-cluster` option and pointing to the backup directory. This will initialize a new, single-member cluster with the default advertised peer URLs, but preserve the entire contents of the etcd data store. Continuing from the previous example: ```sh etcd \ -data-dir=%backup_data_dir% \ [-wal-dir=%backup_wal_dir%] \ - -force-new-cluster \ + --force-new-cluster \ ... ```