From c817df1d3274530af800a75a67cbb9c2de44e609 Mon Sep 17 00:00:00 2001 From: Gyu-Ho Lee Date: Wed, 9 Nov 2016 00:55:52 -0800 Subject: [PATCH] etcdserver: increase maxGapBetweenApplyAndCommitIndex This exists to prevent sending too many requests that would lead into applier falling behind Raft accepting-proposal. Based on recent benchmarks, etcd was able to process high workloads (2 million writes with 1K concurrent clients). The limit 1000 is too conservative to test those high workloads. --- etcdserver/v3_server.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/etcdserver/v3_server.go b/etcdserver/v3_server.go index 55a1d764c..e18bac950 100644 --- a/etcdserver/v3_server.go +++ b/etcdserver/v3_server.go @@ -47,7 +47,7 @@ const ( // the applied index and committed index. // However, if the committed entries are very heavy to apply, the gap might grow. // We should stop accepting new proposals if the gap growing to a certain point. - maxGapBetweenApplyAndCommitIndex = 1000 + maxGapBetweenApplyAndCommitIndex = 5000 ) var (