RockteMQ-AI commented on issue #10827: URL: https://github.com/apache/rocketmq/issues/10827#issuecomment-5213683896
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** This is a well-documented bug in the Pop orderly consumption retry path. The failure chain is clear: **Root Cause:** When a retry request with the same `attemptId` collides with the `group@topic` serial lock (`PopConsumerLockService.tryLock`), it fails fast with an empty return. This pushes the retry into long polling, consumes the re-entry opportunity, and ultimately causes queue-head blocking. **Impact:** - Queue-head blocking for up to `invisibleTime` (or ~3h with autoRenew) - Affects Pop FIFO consumption path with lock contention - Real-world case: gRPC client via Proxy experiencing intermittent long stalls **Severity:** High — affects message consumption liveness in ordered message scenarios **Fix Assessment:** The proposed fix (retry the lock acquisition instead of fail-fast for same-attemptId requests) is minimal, targeted, and preserves existing semantics. The verification with unit tests and real environment testing is thorough. This issue is ready for maintainer review and merge. --- *Automated evaluation by github-manager* -- 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]
