From 968f3d97114da75368b017f79f59b69367355373 Mon Sep 17 00:00:00 2001 From: Giuseppe Lavagetto Date: Sat, 25 Apr 2015 18:54:29 +0200 Subject: [PATCH] docs: clarify the disaster recovery guide A bit was missing from the documentation on disaster recovery, the reset of the advertised peer urls for the node recovered from backup. Without that, any subsequent server joining the cluster would not be able to speak to the first node. --- Documentation/admin_guide.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/admin_guide.md b/Documentation/admin_guide.md index 41d6b3931..fef49d1eb 100644 --- a/Documentation/admin_guide.md +++ b/Documentation/admin_guide.md @@ -61,7 +61,7 @@ After your cluster is up and running, adding or removing members is done via [ru ### Member Migration -When there is a scheduled machine maintenance or retirement, you might want to migrate an etcd member to another machine without losing the data and changing the member ID. +When there is a scheduled machine maintenance or retirement, you might want to migrate an etcd member to another machine without losing the data and changing the member ID. The data directory contains all the data to recover a member to its point-in-time state. To migrate a member: @@ -102,7 +102,7 @@ $ sudo systemctl stop etcd #### Copy the data directory of the now-idle member to the new machine ``` -$ tar -cvzf node1.etcd.tar.gz /var/lib/etcd/node1.etcd +$ tar -cvzf node1.etcd.tar.gz /var/lib/etcd/node1.etcd ``` ``` @@ -181,7 +181,9 @@ Once you have verified that etcd has started successfully, shut it down and move #### Restoring the cluster -Now that the node is running successfully, you can add more nodes to the cluster and restore resiliency. See the [runtime configuration](runtime-configuration.md) guide for more details. +Now that the node is running successfully, you should [change its advertised peer URLs](other_apis.md#change-the-peer-urls-of-a-member), as the `--force-new-cluster` has set the peer URL to the default (listening on localhost). + +You can then add more nodes to the cluster and restore resiliency. See the [runtime configuration](runtime-configuration.md) guide for more details. ### Client Request Timeout