fix(server): reduce the screaming heartbeat logs

Currently the only way we know that a peer isn't getting a heartbeat is an
edge triggered event from go raft on every missed heartbeat. This means that
we need to do some book keeping in order to do exponential backoff.

The upside is that instead of screaming thousands of log lines before a 
machine hits the default removal of 30 minutes it is only ~100.
Sure. That is a better idea.
On Jun 7, 2014 10:37 AM, "Xiang Li" <notifications@github.com> wrote:

> In server/peer_server.go:
>
> >  		}
> > -		log.Infof("%s: warning: heartbeat timed out: '%v'", s.Config.Name, name)
>
> @philips <https://github.com/philips> Can we check the lastActivity here.
> If the lastActivity is smaller than the next backoff and greater than the
> previous backoff, we should reset the backoff. So we probably do not need
> to monitor routine?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coreos/etcd/pull/836/files#r13520506>.
>