RockteMQ-AI commented on issue #10955: URL: https://github.com/apache/rocketmq/issues/10955#issuecomment-5394911152
**Issue Evaluation** Category: `bug` | Status: **Needs Info** Thank you for the detailed report with timestamps and queue-level analysis. A few clarifications are needed before verification can proceed: 1. **Version mismatch**: Server is 4.9.7, client is 4.7.1 — could you confirm if this issue is reproducible with matched versions (e.g., both 4.9.7)? 2. **Consumer startup pattern**: You mention starting the consumer every hour and shutting down after consumption completes. Could you clarify whether the `CONSUME_FROM_LAST_OFFSET` strategy is applied on each fresh start, and whether the offset is persisted to the broker or only in memory? 3. **Reproducibility**: Has this been observed more than once? Is it specific to broker-b queue 5, or has it occurred on other queues/brokers? 4. **TRACE data**: You mention TRACE is enabled but no consumption TRACE exists for the lost message. Does the TRACE data show the message was successfully stored (bornTimestamp matches)? The scenario you describe — where a message at offset 9 is skipped while offsets 0-8 and 10-14 are consumed — suggests a potential offset calculation issue during consumer startup with `CONSUME_FROM_LAST_OFFSET` in ordered consumption mode. This warrants investigation. --- *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]
