[
https://issues.apache.org/jira/browse/FLINK-26254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497451#comment-17497451
]
Alexander Preuss commented on FLINK-26254:
------------------------------------------
Added some testcases
[here|https://github.com/alpreu/flink/commit/a4c1b4b5dd8049e4bec6b2cc6f0b8ddfd500d065]
that could maybe provoke the exception to happen, yet still always pass. We
believe the issue to be on RedPandas side
> 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.15.0, 1.14.3
> 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.1#820001)
