You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2016/12/09 13:53:59 UTC

[jira] [Assigned] (KAFKA-4431) HeartbeatThread should be a daemon thread

     [ https://issues.apache.org/jira/browse/KAFKA-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram reassigned KAFKA-4431:
-------------------------------------

    Assignee: Rajini Sivaram

> HeartbeatThread should be a daemon thread
> -----------------------------------------
>
>                 Key: KAFKA-4431
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4431
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.10.1.0
>            Reporter: David Judd
>            Assignee: Rajini Sivaram
>
> We're seeing an issue where an exception inside the main processing loop of a consumer doesn't cause the JVM to exit, as expected (and, in our case, desired). From the thread dump, it appears that what's blocking exit is the "kafka-coordinator-heartbeat-thread", which is not currently a daemon thread. Per the mailing list, it sounds like this is a bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)