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
{{ message }}
This repository has been archived by the owner on Mar 28, 2020. It is now read-only.
The etcd member can occasionally fail to bootstrap (and exit), by failing to talk to another member due to a dail tcp timeout.
# Logs of etcd member test-etcd-m2pfm-0001
etcdserver: could not get cluster response from http://test-etcd-m2pfm-0000.test-etcd-m2pfm.e2e-etcd-operator-flake-164.svc.cluster.local:2380: Get http://test-etcd-m2pfm-0000.test-etcd-m2pfm.e2e-etcd-operator-flake-164.svc.cluster.local:2380/members:
dial tcp: i/o timeout
etcdmain: cannot fetch cluster info from peer urls: could not retrieve cluster information from the given urls
If this happens for the 2nd member added to the cluster, it can lose quorum and go into disaster recovery.
The exact cause for the dial tcp timeout is not known. Putting this issue as a reference in case we encounter the above problem more frequently.
The text was updated successfully, but these errors were encountered:
The etcd member can occasionally fail to bootstrap (and exit), by failing to talk to another member due to a dail tcp timeout.
If this happens for the 2nd member added to the cluster, it can lose quorum and go into disaster recovery.
The exact cause for the dial tcp timeout is not known. Putting this issue as a reference in case we encounter the above problem more frequently.
The text was updated successfully, but these errors were encountered: