RockteMQ-AI commented on issue #4330: URL: https://github.com/apache/rocketmq-dashboard/issues/4330#issuecomment-5680642322
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** Dashboard backend (new service + controller) + frontend (new modal) **Compatibility:** No breaking changes — additive feature Consumer group rebalance history and partition flapping analysis is a high-value diagnostic feature. Rebalance storms and partition flapping are among the most common causes of consumer lag spikes and message processing delays. **Assessment:** - The problem is well-identified — partition flapping (rapid assign/revoke cycles) is a subtle but impactful issue that is hard to diagnose with current tools - The proposed `ConsumerGroupRebalanceReport` model captures the key indicators (flap count, stability score, average hold duration, top flapping partitions) - The stability score (0-100) is a good abstraction for quick health assessment - **Implementation note:** Rebalance events are typically logged by the broker but not persisted in a queryable format. The implementation may need to either: (a) parse broker logs, (b) add a rebalance event hook in the broker, or (c) track rebalance events at the dashboard level by polling consumer connection data - The historical trend view (1h/6h/24h/7d) is practical for both incident response and capacity planning This feature would significantly improve the dashboard's diagnostic capabilities for consumer-side issues. --- *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]
