[
https://issues.apache.org/jira/browse/KAFKA-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Hauch resolved KAFKA-5774.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Indeed, this was [fixed with this PR|https://github.com/apache/kafka/pull/3639]
as mentioned above:
https://github.com/apache/kafka/blob/11afff09908035166febf9b75c410112693ff98c/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/WorkerSinkTask.java#L515
> 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
> Fix For: 1.0.0
>
>
> 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)
