Scott Reynolds created KAFKA-8229:
-------------------------------------
Summary: Connect Sink Task updates nextCommit when commitRequest
is true
Key: KAFKA-8229
URL: https://issues.apache.org/jira/browse/KAFKA-8229
Project: Kafka
Issue Type: Bug
Reporter: Scott Reynolds
Today, when a WorkerSinkTask uses context.requestCommit(), the next call to
iteration will cause the commit to happen. As part of the commit execution it
will also change the nextCommit milliseconds.
This creates some weird behaviors when a SinkTask calls context.requestCommit
multiple times. In our case, we were calling requestCommit when the number of
kafka records we processed exceed a threshold. This resulted in the nextCommit
being several days in the future and caused it to only commit when the record
threshold was reached.
We expected the task to commit when the record threshold was reached OR when
the timer went off.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
