From c8b5d47f24b3e017ff1e373b93f562545aa0d448 Mon Sep 17 00:00:00 2001 From: Peter Rosell Date: Thu, 5 Feb 2015 22:45:55 +0100 Subject: [PATCH] Documentation: Correct defaults for heartbeat and election Defaults for hearbeat-interval and election-timeout is updated according to configuration documentation. --- Documentation/tuning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/tuning.md b/Documentation/tuning.md index d2a5e7d3c..bd51a0148 100644 --- a/Documentation/tuning.md +++ b/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*. 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. -By default, etcd uses a `50ms` heartbeat interval. +By default, etcd uses a `100ms` heartbeat interval. 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. -By default, etcd uses a `200ms` election timeout. +By default, etcd uses a `1000ms` election timeout. 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.