RockteMQ-AI commented on issue #11168: URL: https://github.com/apache/rocketmq/issues/11168#issuecomment-5680622490
**Issue Evaluation** Category: | Status: **Confirmed** Thank you for the thorough analysis. This is a well-documented report covering six distinct defects in the tiered storage commit path, backed by production log evidence (7,379 error occurrences over 24h). **Summary of confirmed defects:** | # | Defect | Severity | |---|--------|----------| | 1 | Transient upload failure misreported as due to collision with | Medium — misleading diagnostics | | 2 | performs blocking on Netty IO thread | High — stalls all object storage I/O on the broker | | 3 | Three differently worded log messages for the same failure mode | Low — log noise / operator confusion | | 4 | logs // even when the exception is not a , producing misleading local-only values | Medium — diagnostic corruption | | 5 | catch block masks without restoring interrupt flag | Low — potential shutdown delay | **Root cause:** The default of collides with the sentinel, and the callback runs on the completing thread (Netty IO) without executor isolation. **Impact:** Tiered storage users on S3-style backends (OSS, MinIO, etc.) experience misleading error diagnostics and potential IO thread stalls under transient network failures. **Recommendation:** These fixes are well-scoped and suitable for a single PR. An automated fix proposal can be generated. Reply to proceed with PR generation, or provide feedback if you would like to handle this differently. --- *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]
