You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If peer can't be timely reached, the new member dial timeout too quickly in around ~ 1s. The reason for this is because the round tripper prt used has cfg.peerDialTimeout() configured with a small timeout.
func (c*ServerConfig) peerDialTimeout() time.Duration {
// 1s for queue wait and system delay// + one RTT, which is smaller than 1/5 election timeoutreturntime.Second+time.Duration(c.ElectionTicks)*time.Duration(c.TickMs)*time.Millisecond/5
}
this dial timeout seems a bit short for bootstrapping an new etcd member. In the case of etcd-operator, new member might not able reach to existing cluster due to network issue. It will be the best if dial timeout can be configurable to help debugging the underlying network issue.
The text was updated successfully, but these errors were encountered:
etcd version: 3.1.8
via coreos/etcd-operator#1300
When adding a new member to existing cluster, the new member needs to get cluster information from its peer.
https://github.com/coreos/etcd/blob/master/etcdserver/server.go#L312-L315
If peer can't be timely reached, the new member dial timeout too quickly in around ~ 1s. The reason for this is because the round tripper
prt
used hascfg.peerDialTimeout()
configured with a small timeout.https://github.com/coreos/etcd/blob/master/etcdserver/config.go#L183-L187
https://github.com/coreos/etcd/blob/master/etcdserver/server.go#L294
this dial timeout seems a bit short for bootstrapping an new etcd member. In the case of etcd-operator, new member might not able reach to existing cluster due to network issue. It will be the best if dial timeout can be configurable to help debugging the underlying network issue.
The text was updated successfully, but these errors were encountered: