elephone-184 opened a new issue, #4328: URL: https://github.com/apache/rocketmq-dashboard/issues/4328
### Feature Description CommitLog and ConsumeQueue physical disk exhaustion is one of the most severe cluster-level incidents in RocketMQ, triggering write-rejections when reaching `diskMaxUsedSpaceRatio`. Operational teams need proactive capacity forecasting, message retention expiry modeling, and time-to-exhaustion projections before disk space reaches dangerous thresholds. ### Proposed Solution 1. Introduce `BrokerDiskWatermarkReport` model tracking physical mount usage, disk growth velocity (MB/hour), projected exhaustion time, and commitLog deletion watermarks. 2. Implement `BrokerDiskForecasterService` to evaluate storage growth curves and compute auto-expiration timelines. 3. Provide `BrokerDiskForecasterController` with `/cluster/diskForecast.query` endpoint. 4. Add frontend `BrokerDiskForecasterModal` visualizing disk watermarks, linear growth forecasts, and emergency mitigation advice. 5. Provide comprehensive controller and service unit tests. -- 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]
