From 98ff4af7f24b6ed02e9f133e249da38085e65c43 Mon Sep 17 00:00:00 2001 From: Yicheng Qin Date: Fri, 30 May 2014 08:50:16 -0700 Subject: [PATCH] docs(clustering): limit for peer-address changing --- Documentation/clustering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/clustering.md b/Documentation/clustering.md index c6b16305d..1bf197867 100644 --- a/Documentation/clustering.md +++ b/Documentation/clustering.md @@ -107,7 +107,7 @@ curl -L http://127.0.0.1:4001/v2/keys/foo -XPUT -d value=bar If one machine disconnects from the cluster, it could rejoin the cluster automatically when the communication is recovered. -If one machine is killed, it could rejoin the cluster when started with old name. If the peer address is changed, etcd will treat the new peer address as the refreshed one, which benefits instance migration, or virtual machine boot with different IP. +If one machine is killed, it could rejoin the cluster when started with old name. If the peer address is changed, etcd will treat the new peer address as the refreshed one, which benefits instance migration, or virtual machine boot with different IP. The peer-address-changing functionality is only supported when the majority of the cluster is alive, because this behavior needs the consensus of the etcd cluster. **Note:** For now, it is user responsibility to ensure that the machine doesn't join the cluster that has the member with the same name. Or unexpected error will happen. It would be improved sooner or later.