[
https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava resolved KAFKA-4942.
------------------------------------------
Resolution: Fixed
Fix Version/s: 0.11.1.0
0.11.0.0
Issue resolved by pull request 2912
[https://github.com/apache/kafka/pull/2912]
> Kafka Connect: Offset committing times out before expected
> ----------------------------------------------------------
>
> Key: KAFKA-4942
> URL: https://issues.apache.org/jira/browse/KAFKA-4942
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.10.2.0
> Reporter: Stephane Maarek
> Fix For: 0.11.0.0, 0.11.1.0
>
>
> On Kafka 0.10.2.0
> I run a connector that deals with a lot of data, in a kafka connect cluster
> When the offsets are getting committed, I get the following:
> {code}
> [2017-03-23 03:56:25,134] INFO WorkerSinkTask{id=MyConnector-1} Committing
> offsets (org.apache.kafka.connect.runtime.WorkerSinkTask)
> [2017-03-23 03:56:25,135] WARN Commit of WorkerSinkTask{id=MyConnector-1}
> offsets timed out (org.apache.kafka.connect.runtime.WorkerSinkTask)
> {code}
> If you look at the timestamps, they're 1 ms apart. My settings are the
> following:
> {code}
> offset.flush.interval.ms = 120000
> offset.flush.timeout.ms = 60000
> offset.storage.topic = _connect_offsets
> {code}
> It seems the offset flush timeout setting is completely ignored for the look
> of the logs. I would expect the timeout message to happen 60 seconds after
> the commit offset INFO message, not 1 millisecond later.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
