RockteMQ-AI commented on issue #153: URL: https://github.com/apache/rocketmq-operator/issues/153#issuecomment-5216292961
**Issue Evaluation** Category: `question` | Status: **Answered** Operator pod restarts are typically caused by: 1. **Liveness/Readiness probe failures** — If the operator takes too long to reconcile resources, the liveness probe may time out. Check probe configuration: `kubectl describe pod <operator-pod>`. 2. **OOM (Out of Memory)** — The operator may be consuming too much memory during reconciliation of large clusters. Check resource limits and increase if needed. 3. **Leader election** — If running multiple replicas, leader election timeouts can cause restarts. Check logs for `leader election lost` messages. 4. **Webhook failures** — If the operator serves admission webhooks and the webhook service is slow, the pod may be killed. Check the restart reason: ```bash kubectl describe pod <operator-pod> | grep -A5 "Last State" ``` --- *Automated evaluation by @RockteMQ-AI* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
