From 38711761a197b78dfe4a89e471255b6649387570 Mon Sep 17 00:00:00 2001 From: Gyuho Lee Date: Fri, 17 Aug 2018 17:58:08 -0700 Subject: [PATCH] etcdserver: clarify read index wait timeout warnings "read index" doesn't tell much about the root cause. Most likely, the local follower node is having slow network, thus timing out waiting to receive read index response from leader. Signed-off-by: Gyuho Lee --- etcdserver/v3_server.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/etcdserver/v3_server.go b/etcdserver/v3_server.go index 48c345d72f6..092b918b9b0 100644 --- a/etcdserver/v3_server.go +++ b/etcdserver/v3_server.go @@ -693,9 +693,9 @@ func (s *EtcdServer) linearizableReadLoop() { } case <-time.After(s.Cfg.ReqTimeout()): if lg != nil { - lg.Warn("timed out waiting for read index response", zap.Duration("timeout", s.Cfg.ReqTimeout())) + lg.Warn("timed out waiting for read index response (local node might have slow network)", zap.Duration("timeout", s.Cfg.ReqTimeout())) } else { - plog.Warningf("timed out waiting for read index response") + plog.Warningf("timed out waiting for read index response (local node might have slow network)") } nr.notify(ErrTimeout) timeout = true