MAHDI JAFARPUR created KAFKA-16590:
--------------------------------------
Summary: Current offset is higher than last offset
Key: KAFKA-16590
URL: https://issues.apache.org/jira/browse/KAFKA-16590
Project: Kafka
Issue Type: Bug
Reporter: MAHDI JAFARPUR
After a network incident(without any PVC issue or data loss at disk level) in
our data center, we see that the current offset(consumer group offset) of some
partitions in some topics is higher than the last offset(last record offset in
the partition) of that partition.
I read relevant Kafka documents about this issue, then I noticed that this
issue never should happen because when you try to fetch or commit an offset
that doesn't exist(higher or lower than Kafka offset range), Kafka returns an
OffsetOutOfRangeException
also when there is no committed position in the consumer group Kafka will use
{{auto.offset.reset }} configuration. I inquired about this issue with the
Strimzi community, and they confirmed that it is not caused by Strimzi.
Questions:
* Can this issue be from our consumer/producer library(Golang/Sarama)?
* Can this issue be from the Kafka bug or probmel?
h3. Strimzi version
0.33.2
h3. Kubernetes version
K8s: v1.20.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
