Aias00 opened a new issue, #2683: URL: https://github.com/apache/rocketmq-dashboard/issues/2683
## Problem Scheduled query-history cleanup and audit cleanup delete every expired row in one statement. On large installations this can create long transactions, substantial undo/redo work and lock contention. ## Evidence - `server/src/main/java/org/apache/rocketmq/studio/instance/message/QueryHistoryService.java:180` - `server/src/main/java/org/apache/rocketmq/studio/instance/message/QueryHistoryService.java:190` - `server/src/main/java/org/apache/rocketmq/studio/ops/audit/MybatisPlusAuditRepository.java:98` ## Expected behavior - Delete expired rows in bounded batches using an indexed ID/time selection. - Continue until fewer than the configured batch size are removed. - Bound one scheduled pass to avoid monopolizing the database. - Preserve failure isolation between message, trace and audit cleanup. - Add large-inventory and partial-failure regression 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]
