Home Explore Help
Register Sign In
publics
/
etcd-io__etcd
0
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Browse Source

docs(clustering): limit for peer-address changing

Yicheng Qin 11 years ago
parent
b3c5ed60bd
commit
98ff4af7f2
1 changed files with 1 additions and 1 deletions
Unified View Show Diff Stats
  1. 1 1
      Documentation/clustering.md

+ 1 - 1
Documentation/clustering.md
View File 

@@ -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 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.
 
 **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.