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.
Ah! Good point I will just have it log here.
On Jun 7, 2014 9:06 AM, "Yicheng Qin" <notifications@github.com> wrote:

> In server/peer_server.go:
>
> > @@ -691,7 +705,7 @@ func (s *PeerServer) raftEventLogger(event raft.Event) {
> >  		if peer, ok := value.(*raft.Peer); ok {
> >  			name = peer.Name
> >  		}
> > -		log.Infof("%s: warning: heartbeat timed out: '%v'", s.Config.Name, name)
> > +		s.logHeartbeatTimeout(name)
>
> If the peer is not *raft.Peer, it will record it as <unknown> in the log
> and backoff map. But we never delete it in the monitorLogBackoff.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coreos/etcd/pull/836/files#r13520098>.
>