RockteMQ-AI commented on issue #2683: URL: https://github.com/apache/rocketmq-dashboard/issues/2683#issuecomment-5452926174
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `QueryHistoryService`, `MybatisPlusAuditRepository` — scheduled cleanup paths **Compatibility:** No breaking changes; internal batch sizing is additive. Well-identified performance concern. Unbounded `DELETE` on large tables can indeed cause long transactions and lock contention. The proposed approach — bounded batch deletion with a configurable pass limit — is a standard pattern for this class of problem. Key considerations: - Batch size should be configurable (not hardcoded) to accommodate different deployment scales. - Failure isolation between message/trace/audit cleanup is important — each should proceed independently. - Regression tests for partial-failure scenarios will help prevent regressions. This is a solid improvement for large-scale 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]
