-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Description
Description
Hello,
I have deployed apisix 2.7.0 Helm chart and out of three etcd pods, two are going into crash loop back off error which affects the ingress created for other deployments.
The logs show the following details,
Master (etcd pod in running state)
"msg":"rejected stream from remote peer because it was removed","local-member-id"
Other pods (etcd pods in crash loop back off state)
"failed to publish local member to cluster through raft","local-member-id":"2c16fb63879f0d98","local-member-attributes":"{Name:apisix-etcd-1 ClientURLs:[http://apisix-etcd-1.apisix-etcd-headless.apisix.svc.cluster.local:2379/ http://apisix-etcd.apisix.svc.cluster.local:2379]}","request-path":"/0/members/2c16fb63879f0d98/attributes","publish-timeout":"7s","error":"etcdserver: request cancelled"
Currently stuck in this, let me know if anyone has faced this and has any fix for this
Environment
- APISIX version (run
apisix version
): 2.7.0
Metadata
Metadata
Assignees
Labels
Type
Projects
Status