Browse Source

Documentation: Correct defaults for heartbeat and election

Defaults for hearbeat-interval and election-timeout is updated according to configuration documentation.
Peter Rosell 11 years ago
parent
commit
c8b5d47f24
1 changed files with 2 additions and 2 deletions
  1. 2 2
      Documentation/tuning.md

+ 2 - 2
Documentation/tuning.md

@@ -11,11 +11,11 @@ The underlying distributed consensus protocol relies on two separate time parame
 The first parameter is called the *Heartbeat Interval*.
 The first parameter is called the *Heartbeat Interval*.
 This is the frequency with which the leader will notify followers that it is still the leader.
 This is the frequency with which the leader will notify followers that it is still the leader.
 etcd batches commands together for higher throughput so this heartbeat interval is also a delay for how long it takes for commands to be committed.
 etcd batches commands together for higher throughput so this heartbeat interval is also a delay for how long it takes for commands to be committed.
-By default, etcd uses a `50ms` heartbeat interval.
+By default, etcd uses a `100ms` heartbeat interval.
 
 
 The second parameter is the *Election Timeout*.
 The second parameter is the *Election Timeout*.
 This timeout is how long a follower node will go without hearing a heartbeat before attempting to become leader itself.
 This timeout is how long a follower node will go without hearing a heartbeat before attempting to become leader itself.
-By default, etcd uses a `200ms` election timeout.
+By default, etcd uses a `1000ms` election timeout.
 
 
 Adjusting these values is a trade off.
 Adjusting these values is a trade off.
 Lowering the heartbeat interval will cause individual commands to be committed faster but it will lower the overall throughput of etcd.
 Lowering the heartbeat interval will cause individual commands to be committed faster but it will lower the overall throughput of etcd.