Replies: 1 comment
-
I wonder if it is due to: " It is unsafe to remove a member from a two member cluster. The majority of a two member cluster is also two." from https://etcd.io/docs/v3.3/op-guide/runtime-configuration/ ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I added a node and was unable to get instance started on the remote server so I want to remove it from the cluster, but removal is failing
member list works:
etcdctl --endpoints=http://10.213.214.122:2181 member list
b0e8230fea532c53, unstarted, , http://10.213.110.101:2380,
fba93e16963ab1c3, started, etcd-1, http://10.213.214.122:2380, http://10.213.214.122:2181
Remove fails
etcdctl --endpoints=http://10.213.214.122:2181 member remove b0e8230fea532c53
Error: context deadline exceeded
etcdctl --endpoints=http://10.213.214.122:2181 member remove b0e8230fea532c53
Error: context deadline exceeded
When I look at logs of the healthy node I can see:
{"level":"warn","ts":"2022-10-05T23:45:28.164Z","caller":"v3rpc/interceptor.go:197","msg":"request stats","start time":"2022-10-05T23:45:23.165Z","time spent":"4.999684243s","remote":"10.213.214.122:50849","response type":"/etcdserverpb.Cluster/MemberRemove","request count":-1,"request size":-1,"response count":-1,"response size":-1,"request content":""}
WARNING: 2022/10/05 23:45:28 [core] grpc: Server.processUnaryRPC failed to write status: connection error: desc = "transport is closing"
It tries to delete it but fails for some reason. I am not sure what is going on because there is limited error logs.
I am using latest bitnami docker image and etcdctl 3.2.7
Is there any way I can debug why my remove request is timing out?
Beta Was this translation helpful? Give feedback.
All reactions