[
https://issues.apache.org/jira/browse/FLINK-35630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855813#comment-17855813
]
Martijn Visser commented on FLINK-35630:
----------------------------------------
[~tanjialiang] Do you have a reproducible scenario, because this would indicate
a problem for all Kafka consumers, not so much Flink. Flink is just using the
Kafka consumer under the hood in this case.
> 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
> Priority: Major
>
> 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)
