[ 
https://issues.apache.org/jira/browse/KAFKA-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423239#comment-15423239
 ] 
ASF GitHub Bot commented on KAFKA-4042:
---------------------------------------

GitHub user shikhar opened a pull request:

    https://github.com/apache/kafka/pull/1745

    WIP: KAFKA-4042: prevent DistributedHerder thread from dying from 
connector/task lifecycle exceptions

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shikhar/kafka distherder-stayup

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1745.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1745
    
----
commit 715e7535d4aaae6174b3d6c1607617b382f0a8b8
Author: Shikhar Bhushan <shik...@confluent.io>
Date:   2016-08-16T19:06:56Z

    KAFKA-4042: prevent DistributedHerder thread from dying from connector/task 
lifecycle exceptions

----


> 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
>          Components: KafkaConnect
>            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)

Reply via email to