RockteMQ-AI commented on issue #2000: URL: https://github.com/apache/rocketmq-dashboard/issues/2000#issuecomment-5265328533
**Issue Evaluation** Category: | Status: **Confirmed** The concurrency issue is valid. returning while discarding the MyBatis-Plus affected-row count means concurrent deletes cannot detect the lost race. The second delete silently succeeds after removing zero rows, then proceeds to release runtime clients and record a false audit event. **Root Cause:** discards the return from , and has no way to detect a zero-row delete. **Impact:** Instance lifecycle integrity — phantom deletions can release shared AdminClient endpoints and create misleading audit trails. **Severity:** medium — requires concurrent requests to trigger, but the window is real in production with retry logic or UI double-clicks. **Suggested fix aligns with the report:** propagate the affected-row count from the repository layer and map zero rows to a 404 before any post-delete side effects (client release, audit). An automated fix proposal will be generated. Reply to proceed with PR generation. --- *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]
