RockteMQ-AI commented on issue #4341: URL: https://github.com/apache/rocketmq-dashboard/issues/4341#issuecomment-5680637265
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** Dashboard backend (new service + controller) + frontend (new modal component) **Compatibility:** No breaking changes — additive feature This is a well-structured feature request for cross-cluster topic configuration drift detection and rectification. The proposed architecture (model → service → controller → frontend modal) follows the existing dashboard patterns. **Assessment:** - The use case is valid — configuration drift in dual-DC setups is a real operational pain point - The proposed 5-step implementation plan is reasonable and follows dashboard conventions - Key consideration: the dashboard would need admin credentials for multiple clusters to perform cross-cluster comparisons. Access control and credential management should be addressed in the implementation - The `TopicCrossClusterSyncReport` model should include timestamp and last-sync status for auditability This feature would benefit from discussion with RocketMQ core maintainers on whether the comparison should be limited to topic attributes or also cover consumer group configurations. --- *Automated evaluation by github-manager-bot* -- 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]
