RockteMQ-AI commented on issue #239: URL: https://github.com/apache/rocketmq-operator/issues/239#issuecomment-5364747256
**Issue Evaluation** Category: `question` This is a question about scale-down behavior in the RocketMQ Operator. Currently, the RocketMQ Operator does not fully support automatic cleanup when scaling down Broker replicas (e.g., from size 2 to 1). The remaining StatefulSet pod retains its ordinal index, and the removed pod's data (CommitLog, ConsumeQueue) is not automatically migrated or cleaned up. **Current behavior:** - Scaling down removes the highest-ordinal pod - The old pod's PVC may remain (depending on `persistentVolumeClaimRetentionPolicy`) - Queue assignments on the removed broker need to be rebalanced by consumers **Recommendation:** - Before scaling down, ensure all message queues on the target broker have been migrated - Use `mqadmin updateSubGroup` and `mqadmin deleteTopic` to clean up if needed - This is a known limitation — consider filing a feature request for automated scale-down with data migration --- *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]
