FrankChen021 commented on issue #11658:
URL: https://github.com/apache/druid/issues/11658#issuecomment-982606004
@samarthjain You have run into exact problem I described in this issue.
Since the `earliestOffset` is 2944387224, but the `nextOffset` is
22400192044, the code goes into this block
```
if (leastAvailableOffset > nextOffset) {
doReset = true;
resetPartitions.put(topicPartition, nextOffset);
}
```
Notice that here `nextoffset` holds the position where the offset will be
reset to, but obvisouly, the valid offset is 2944387224, so the offset won't
success. In the poll period, the consumer tries to read the topic from the
wrong offset, which results in `outOfRangePartition` again.
So the kafka ingestion does reset again and again, this is what I mean a
'dead loop'.
This problem usually happens when the Kafka partition expires before Druid
reads message from it.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
