[
https://issues.apache.org/jira/browse/FLINK-26254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser closed FLINK-26254.
----------------------------------
Resolution: Fixed
Verified that this issue no longer occurs with Flink 1.16.0 and the latest
version of Redpanda. Most likely this was resolved because Flink has updated to
a newer version of the Kafka Client.
> KafkaSink might violate order of sequence numbers and risk exactly-once
> processing
> ----------------------------------------------------------------------------------
>
> Key: FLINK-26254
> URL: https://issues.apache.org/jira/browse/FLINK-26254
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.14.3, 1.15.0
> Reporter: Fabian Paul
> Assignee: Alexander Preuss
> Priority: Critical
>
> When running the KafkaSink in exactly-once mode with a very low checkpoint
> interval users are seeing `OutOfOrderSequenceException`.
> It could be caused by the fact that the connector has a pool of
> KafkaProducers and the sequence numbers are not shared/reset if a new
> KafkaProducer tries to write to a partition while the previous KafkaProducer
> is still occupied for committing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
