RockteMQ-AI commented on issue #161: URL: https://github.com/apache/rocketmq-operator/issues/161#issuecomment-5216280683
**Issue Evaluation** Category: `bug` | Status: **Needs Investigation** When deploying brokers with three masters and three slaves, all pods being scheduled to the same node defeats the purpose of high availability. This is likely caused by missing `podAntiAffinity` rules in the StatefulSet/Deployment specs generated by the operator. **Expected Fix:** - Add `podAntiAffinity` with `preferredDuringSchedulingIgnoredDuringExecution` (or `requiredDuringSchedulingIgnoredDuringExecution` for strict HA) to ensure master and slave pods of the same broker group are spread across different nodes. **Impact:** High — single node failure could take down both master and slave, causing message loss. **Severity:** High — affects data reliability in production deployments. --- *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]
