RisingWave Community - What steps should I take to resolve the 'CrashLoopBackOff' issue in my RisingWave Operator cluster after a Kubernetes restart?

RisingWave Community

risingwave-community.slack.com

troubleshooting

What steps should I take to resolve the 'CrashLoopBackOff' issue in my RisingWave Operator cluster after a Kubernetes restart?

I'm facing a 'CrashLoopBackOff' issue in my RisingWave Operator cluster after a Kubernetes restart. The meta node is showing errors related to another cluster using the bucket. I haven't persisted the etcd data. Should I just remove 'clusterid/0' or do I need to take additional steps like clearing the S3 directory before recreating the cluster?

Jesue

Asked on Mar 29, 2024

Confirm if etcd data was persisted during the Kubernetes restart.
Removing 'clusterid/0' should resolve the 'CrashLoopBackOff' issue.
It is recommended to clear the S3 directory before recreating the cluster to avoid potential errors related to data conflicts.

Mar 29, 2024Edited by