[
https://issues.apache.org/jira/browse/KAFKA-13927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585652#comment-17585652
]
Jordan Bull commented on KAFKA-13927:
-------------------------------------
I've also encountered this. This is especially problematic when the stream is
bursty and the last batch of messages encounters a RetriableException. In such
a case, the offsets will never be committed resulting in sustained lag.
Proposed fix in
https://github.com/apache/kafka/pull/12566/commits/109ad70e20206cc82ebb155776b42e547cdd243d
> Kafka Connect Sink Connector Success after RetriableException, no commit
> offset to remote.
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-13927
> URL: https://issues.apache.org/jira/browse/KAFKA-13927
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.8.0
> Reporter: gj choi
> Priority: Minor
>
> I made a custom SinkConnector.
> and I set retries with RetriableException.
>
> In normal case, successfully offset commited with no LAG.
> but one or more RetriableException occured and then, retry make success
> there are LAG about sucess record, despite the retry success.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
