[
https://issues.apache.org/jira/browse/KAFKA-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shikhar Bhushan updated KAFKA-4042:
-----------------------------------
Description: As one example, there isn't exception handling in
{{DistributedHerder.startConnector()}} or the call-chain for it originating in
the {{tick()}} on the herder thread, and it can throw an exception because of a
bad class name in the connector config. (report of issue in wild:
https://groups.google.com/d/msg/confluent-platform/EnleFnXpZCU/3B_gRxsRAgAJ)
(was: While errors in {{WorkerConnector}} are handled using the
{{statusListener.onFailure()}} callback, before the {{WorkerConnector}} is
created in {{Worker.startConnector()}} there can be exceptions because of e.g.
a bad class name and these are currently not handled, causing the {{Herder}}
thread to die.
Report of issue in wild:
https://groups.google.com/d/msg/confluent-platform/EnleFnXpZCU/3B_gRxsRAgAJ)
> DistributedHerder thread can die because of connector & task lifecycle
> exceptions
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-4042
> URL: https://issues.apache.org/jira/browse/KAFKA-4042
> Project: Kafka
> Issue Type: Bug
> Reporter: Shikhar Bhushan
> Assignee: Shikhar Bhushan
>
> As one example, there isn't exception handling in
> {{DistributedHerder.startConnector()}} or the call-chain for it originating
> in the {{tick()}} on the herder thread, and it can throw an exception because
> of a bad class name in the connector config. (report of issue in wild:
> https://groups.google.com/d/msg/confluent-platform/EnleFnXpZCU/3B_gRxsRAgAJ)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
