Re: [I] Fix OFFSET_ILLEGAL error when RmqSourceTask pulls messages [rocketmq-connect]

["RockteMQ-AI (via GitHub)" <gi...@apache.org>]

RockteMQ-AI commented on issue #330:
URL: https://github.com/apache/rocketmq-connect/issues/330#issuecomment-5431182794

   **Issue Evaluation**
   
   Category: `bug` | Status: **Evaluated**
   
   This reports that when `RmqSourceTask` receives an `OFFSET_ILLEGAL` response during message pulling, the pull operation becomes blocked instead of recovering gracefully.
   
   **Assessment:** `OFFSET_ILLEGAL` typically occurs when the consumer's offset is out of range (e.g., the queue has been truncated or the offset points to deleted messages). The expected behavior should be to reset the offset to the nearest valid position (min or max offset) and resume pulling, rather than blocking indefinitely.
   
   **Root Cause (likely):** The `RmqSourceTask` pull logic may not handle the `OFFSET_ILLEGAL` response code with proper offset reset semantics, causing the task to stall.
   
   **Suggested Fix:** Add handling for `OFFSET_ILLEGAL` in the pull callback to reset the offset to `broker.getMinOffset()` or `broker.getMaxOffset()` depending on the direction, then resume pulling.
   
   ---
   *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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org