[
https://issues.apache.org/jira/browse/KAFKA-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272163#comment-17272163
]
Chris Egerton commented on KAFKA-12182:
---------------------------------------
[~FatimaG] this seems like it may be a duplicate of KAFKA-5756. Could you take
a look and see if the recent comments on there align with what you're
experiencing?
KAFKA-5756 only comes up when a task is already failing for a different reason;
the root cause for the failure gets masked by the offset writer exception. The
root cause is likely to be connector-dependent and it's difficult to say for
sure whether the Debezium article you linked is applicable here since the stack
trace doesn't provide insight into that. You may want to reach out to the
Debezium community for help with this issue, probably with a log sample for the
connector and its tasks since that should contain more info.
> Kafka connector is failing due to ' OffsetStorageWriter is already flushing'
> error
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-12182
> URL: https://issues.apache.org/jira/browse/KAFKA-12182
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Environment: QAS
> Reporter: Fátima Galera
> Priority: Major
>
> Hi kafka support
>
> We have a connector which is failing with below error
>
> "state": "FAILED",
> "worker_id": "xxxxxx:8083",
> "trace": "org.apache.kafka.connect.errors.ConnectException:
> OffsetStorageWriter is already flushing\n\tat
> org.apache.kafka.connect.storage.OffsetStorageWriter.beginFlush(OffsetStorageWriter.java:111)\n\tat
>
> org.apache.kafka.connect.runtime.WorkerSourceTask.commitOffsets(WorkerSourceTask.java:410)\n\tat
>
> org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:239)\n\tat
> org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175)\n\tat
> org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219)\n\tat
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\n\tat
> java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
> java.lang.Thread.run(Thread.java:748)\n"
>
> I have read below article about this issue, but this is old. Could you please
> let us know if we should implement these parameters?
>
> [https://stackoverflow.com/questions/55839310/debezium-is-failing-to-snapshot-big-table-size]
>
> Best regards and thanks
> Fátima
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
