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
Help! The same command executed on cluster machine k8s-master01 produces different results than on the other two cluster machines. k8s-master01 reports an error: 'Error: context deadline exceeded', but the other two cluster machines display normally.
10.10.10.11:
# command1:export ETCDCTL_API=3
etcdctl --endpoints="https://10.10.10.13:2379,https://10.10.10.12:2379,https://10.10.10.11:2379" --cacert=/etc/kubernetes/pki/etcd/etcd-ca.pem --cert=/etc/kubernetes/pki/etcd/etcd.pem --key=/etc/kubernetes/pki/etcd/etcd-key.pem member list
# output1:
{"level":"warn","ts":"2024-08-22T11:22:04.788108+0800","logger":"etcd-client","caller":"v3@v3.5.13/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00056e000/10.10.10.13:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
Error: context deadline exceeded
# command2:
etcdctl --endpoints="10.10.10.13:2379,10.10.10.12:2379,10.10.10.11:2379" --cacert=/etc/kubernetes/pki/etcd/etcd-ca.pem --cert=/etc/kubernetes/pki/etcd/etcd.pem --key=/etc/kubernetes/pki/etcd/etcd-key.pem endpoint status
# output2:
{"level":"warn","ts":"2024-08-22T11:24:18.395893+0800","logger":"etcd-client","caller":"v3@v3.5.13/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0004d8000/10.10.10.13:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
Failed to get the status of endpoint 10.10.10.13:2379 (context deadline exceeded)
{"level":"warn","ts":"2024-08-22T11:24:23.396922+0800","logger":"etcd-client","caller":"v3@v3.5.13/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0004d8000/10.10.10.13:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
Failed to get the status of endpoint 10.10.10.12:2379 (context deadline exceeded)
{"level":"warn","ts":"2024-08-22T11:24:28.398746+0800","logger":"etcd-client","caller":"v3@v3.5.13/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0004d8000/10.10.10.13:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = context deadline exceeded"}
Failed to get the status of endpoint 10.10.10.11:2379 (context deadline exceeded)
# command3:
etcdctl member list
# output3:
4776526eb1c8ce1a, started, k8s-master02, https://10.10.10.12:2380, https://10.10.10.12:2379, false
4d0649dd161f73d8, started, k8s-master01, https://10.10.10.11:2380, https://10.10.10.11:2379, false
c6eaa306941ff399, started, k8s-master03, https://10.10.10.13:2380, https://10.10.10.13:2379, false# command4:
etcdctl endpoint status
# output4:
127.0.0.1:2379, 4d0649dd161f73d8, 3.5.13, 20 kB, false, false, 5, 46, 46,
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
ENV
cluster
k8s-master01: 10.10.10.11, k8s-master02: 10.10.10.12, k8s-master03: 10.10.10.13
etcdctl version
etcdctl version: 3.5.13
API version: 3.5
service-file
/usr/lib/systemd/system/etcd.service
config-file
/etc/etcd/etcd.config.yml
problem
Help! The same command executed on cluster machine k8s-master01 produces different results than on the other two cluster machines. k8s-master01 reports an error: 'Error: context deadline exceeded', but the other two cluster machines display normally.
10.10.10.11:
10.10.10.12 / 10.10.10.13:
Beta Was this translation helpful? Give feedback.
All reactions