[
https://issues.apache.org/jira/browse/KAFKA-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116962#comment-16116962
]
Oleg Kuznetsov commented on KAFKA-5696:
---------------------------------------
[~rhauch] Thank you for detailed explanation.
But aren't offsets committed also at the end of every poll() method?
I found this in WorkerSourceTask.execute() finally block.
{code:java}
} finally {
// It should still be safe to commit offsets since any exception
would have
// simply resulted in not getting more records but all the existing
records should be ok to flush
// and commit offsets. Worst case, task.flush() will also throw an
exception causing the offset commit
// to fail.
commitOffsets();
}
{code}
> SourceConnector does not commit offset on rebalance
> ---------------------------------------------------
>
> Key: KAFKA-5696
> URL: https://issues.apache.org/jira/browse/KAFKA-5696
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Oleg Kuznetsov
> Labels: newbie
> Fix For: 0.10.0.2
>
>
> I'm running SourceConnector, that reads files from storage and put data in
> kafka. I want, in case of reconfiguration, offsets to be flushed.
> Say, a file is completely processed, but source records are not yet committed
> and in case of reconfiguration their offsets might be missing in store.
> Is it possible to force committing offsets on reconfiguration?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
