satishd commented on PR #15060: URL: https://github.com/apache/kafka/pull/15060#issuecomment-1882487316
@iit2009060 The behaviour that you mentioned in the [comment](https://github.com/apache/kafka/pull/15060#issuecomment-1879657273) seems to be working as expected. The client seems to be receiving OffsetOutOfRangeException. When a consumer client sends a request for fetch offset that is out of range then it receives offset out of range error and it sends the next request based on `auto-offset-reset` strategy that is set on the consumer client. It seems the default value for `kafka-console-consumer` is `latest` if not set through an `auto.offset.reset` property or does not use `--from-beginning` argument. In your case, it may be trying to fetch the latest offset in the next request and there are no messages published to the topic beyond that offset as there may not be any more messages published after that offset. You can try running the same scenario of fetching out of range offset 1 with `--from-beginning` and observe the behavior. We can syncup offline to understand your scenario better. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
