mirror of
https://github.com/etcd-io/etcd.git
synced 2024-09-27 06:25:44 +00:00
Merge pull request #2241 from peterrosell/correct_defaults_in_tuning
Correct defaults for heartbeat and election
This commit is contained in:
commit
e2feafc741
@ -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.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user