search

bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
8.88k stars 9.16k forks source link

[bitnami/apisix] Apisix ETCD going into Crash loop back off #27444

Closed Lakshmi2k1 closed 2 months ago

Lakshmi2k1 commented 3 months ago

Name and Version

bitnami/etcd 10.1.0

What architecture are you using?

amd64

What steps will reproduce the bug?

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.

image 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

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

The pod keeps restarting

Additional information

No response

javsalgar commented 3 months ago

Hi,

Did you check if there were PVCs from previous deployments?

github-actions[bot] commented 2 months ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

github-actions[bot] commented 2 months ago

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.