You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Gwen Shapira (Jira)" <ji...@apache.org> on 2020/05/25 20:05:00 UTC
[jira] [Resolved] (KAFKA-5000) Framework should log some progress
information regularly to assist in troubleshooting
[ https://issues.apache.org/jira/browse/KAFKA-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira resolved KAFKA-5000.
---------------------------------
Resolution: Fixed
Metrics seem like a better indicator than logs.
> Framework should log some progress information regularly to assist in troubleshooting
> -------------------------------------------------------------------------------------
>
> Key: KAFKA-5000
> URL: https://issues.apache.org/jira/browse/KAFKA-5000
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Gwen Shapira
> Priority: Major
>
> We get many questions of the type:
> "I started a connector, it doesn't seem to make any progress, I don't know what to do"
> I think that periodic "progress reports" on the worker logs may help.
> We have the offset commit message: "INFO WorkerSinkTask{id=cassandra-sink-connector-0} Committing offsets (org.apache.kafka.connect.runtime.WorkerSinkTask:244)"
> But I think we'd also want to know: topic, partition, offsets, how many rows were read from source/kafka and how many were successfully written.
> This will help determine if there is any progress being made and whether some partitions are "stuck" for some reason.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)