Yicheng Qin 8f6bf029f8 etcdserver: specify request timeout error due to connection lost ...

It specifies request timeout error possibly caused by connection lost,
and print out better log for user to understand.

It handles two cases:
1. the leader cannot connect to majority of cluster.
2. the connection between follower and leader is down for a while,
and it losts proposals.

log format:
```
20:04:19 etcd3 | 2015-08-25 20:04:19.368126 E | etcdhttp: etcdserver:
request timed out, possibly due to connection lost
20:04:19 etcd3 | 2015-08-25 20:04:19.368227 E | etcdhttp: etcdserver:
request timed out, possibly due to connection lost
```

2015-08-26 12:38:37 -07:00

..

httptypes

*: test gofmt with -s and fix reported issues

2015-08-21 18:52:16 -07:00

capability.go

etcdhttp: add auth capability in 2.2

2015-08-13 14:49:10 -07:00

client_auth_test.go

etcdserver: handle malformed basic auth

2015-08-25 12:37:24 -07:00

client_auth.go

etcdserver: handle malformed basic auth

2015-08-25 12:37:24 -07:00

client_test.go

*: test gofmt with -s and fix reported issues

2015-08-21 18:52:16 -07:00

client.go

etcdserver: specify request timeout error due to connection lost

2015-08-26 12:38:37 -07:00

http_test.go

etcdserver: refactore member.go

2015-05-21 09:19:29 -07:00

http.go

etcdserver: specify request timeout error due to connection lost

2015-08-26 12:38:37 -07:00

peer_test.go

etcdserver: stop exposing Cluster struct

2015-05-13 10:01:25 -07:00

peer.go

etcdhttp: use leveled logging

2015-06-09 09:26:57 -07:00