Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.4.0
Description
Due to KAFKA-7703, when the Kafka source tries to get the latest offset, it may get an earliest offset, and then it will reprocess messages that have been processed when it gets the correct latest offset in the next batch.
This usually happens when restarting a streaming query.
Attachments
Issue Links
- is caused by
-
KAFKA-7703 KafkaConsumer.position may return a wrong offset after "seekToEnd" is called
- Resolved
- is duplicated by
-
SPARK-28641 MicroBatchExecution committed offsets greater than available offsets
- Closed
- is related to
-
SPARK-28174 Upgrade to Kafka 2.3.0
- Resolved
- links to