[ https://issues.apache.org/jira/browse/KAFKA-9580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041344#comment-17041344 ]
ASF GitHub Bot commented on KAFKA-9580: --------------------------------------- d8tltanc commented on pull request #8144: KAFKA-9580: Log clearer error messages when there is an offset out of range URL: https://github.com/apache/kafka/pull/8144 Log the partition start offset and last stable offset when the subscriptions have the default offset reset policy and the fetch offset is out of index. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Log clearer error messages when there is an offset out of range > --------------------------------------------------------------- > > Key: KAFKA-9580 > URL: https://issues.apache.org/jira/browse/KAFKA-9580 > Project: Kafka > Issue Type: Bug > Components: core > Reporter: Sanjana Kaundinya > Assignee: Cheng Tan > Priority: Major > > Currently in > [Fetcher::initializedCompletedFetch|[https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/Fetcher.java#L1259]], > it's not informative on what offsets are exactly in range, and it makes it > harder to debug when Consumer issues come up in this situation. It would be > much more helpful if we logged a message similar to > [Log::read|[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/log/Log.scala#L1468]] > to make it easier to debug. -- This message was sent by Atlassian Jira (v8.3.4#803005)