You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "tanjialiang (Jira)" <ji...@apache.org> on 2024/06/18 06:55:00 UTC

[jira] [Created] (FLINK-35630) Kafka source may reset the consume offset to earliest when the partition leader changes

tanjialiang created FLINK-35630:
-----------------------------------

             Summary: Kafka source may reset the consume offset to earliest when the partition leader changes
                 Key: FLINK-35630
                 URL: https://issues.apache.org/jira/browse/FLINK-35630
             Project: Flink
          Issue Type: Bug
          Components: Connectors / Kafka
    Affects Versions: kafka-3.2.0
            Reporter: tanjialiang


Kafka producer using the ack=1 option to write data to a topic.

Flink Kafka source startup with the *scan.startup.mode=earliest-offset* option to consume (the Kafka *auto.offset.reset* option will be force override to earliest).

If a partition leader is not available, a follower may become the new leader and this may trigger log truncation. It may cause consumers to consume offset out of range and use the *auto.offset.reset* strategy to reset the offset.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)