You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2017/09/06 18:17:00 UTC
[jira] [Commented] (KAFKA-5774) WorkerSinkTask failure exception
should include cause
[ https://issues.apache.org/jira/browse/KAFKA-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155820#comment-16155820 ]
Ewen Cheslack-Postava commented on KAFKA-5774:
----------------------------------------------
I think this is already fixed in trunk: https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/WorkerSinkTask.java#L488 We are correctly including the cause (and I think it should be logged from the previous log line as well). This happened when I revamped all the logging in the various Worker classes.
> WorkerSinkTask failure exception should include cause
> -----------------------------------------------------
>
> Key: KAFKA-5774
> URL: https://issues.apache.org/jira/browse/KAFKA-5774
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.11.0.0
> Reporter: Randall Hauch
>
> When the WorkerSinkTask shuts down because of a connector exception, the task throws an exception with the message like the following:
> {code}
> ERROR Task Vital-ElasticsearchSinkConnector-0 threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:141)
> org.apache.kafka.connect.errors.ConnectException: Exiting WorkerSinkTask due to unrecoverable exception.
> at org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:451)
> ...
> {code}
> without any information about the exception that caused the task to fail. The cause is logged just prior to this error, but it would be more helpful for the shutdown error message to include the cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)