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

doc: remove one limitation in upgrade doc

Xiang Li 10 years ago
parent
a44da0b62a
commit
3689ea3071
1 changed files with 1 additions and 3 deletions
Unified View Show Diff Stats
  1. 1 3
      Documentation/upgrade_2_2.md

+ 1 - 3
Documentation/upgrade_2_2.md
View File 

@@ -29,9 +29,7 @@ Internally, etcd members negotiate with each other to determine the overall etcd
 
 
 
 #### Limitations
 
 #### Limitations
 
 
 
-It might take up to 2 minutes for the newly upgraded member to catch up with the existing cluster when the total data size is larger than 50MB (You can check the size of the existing snapshot to know about the rough data size). In other words, it is safest to wait for 2 minutes before upgrading the next member.
 
-
 
-If you have even more data, this might take more time. If you have a data size larger than 100MB you should contact us before upgrading, so we can make sure the upgrades work smoothly.
 
+If you have a data size larger than 100MB you should contact us before upgrading, so we can make sure the upgrades work smoothly.
 
 
 
 Every etcd 2.2 member will do health checking across the cluster periodically. etcd 2.1 member does not support health checking. During the upgrade, etcd 2.2 member will log warning about the unhealthy state of etcd 2.1 member. You can ignore the warning. 
 Every etcd 2.2 member will do health checking across the cluster periodically. etcd 2.1 member does not support health checking. During the upgrade, etcd 2.2 member will log warning about the unhealthy state of etcd 2.1 member. You can ignore the warning.