You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/12/12 03:08:58 UTC
[jira] [Resolved] (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 ]
Ismael Juma resolved KAFKA-4431.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.10.2.0
Issue resolved by pull request 2234
[https://github.com/apache/kafka/pull/2234]
> 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
> Fix For: 0.10.2.0
>
>
> 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)