You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 consumer group Kafka will use auto.offset.reset configuration.
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.
Description
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 consumer group Kafka will use
auto.offset.reset
configuration.Question:
Versions
Configuration
Additional Context
related issue: #1734
The text was updated successfully, but these errors were encountered: