You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/09 13:59:58 UTC
[jira] [Commented] (KAFKA-4431) HeartbeatThread should be a daemon
thread
[ https://issues.apache.org/jira/browse/KAFKA-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735393#comment-15735393 ]
ASF GitHub Bot commented on KAFKA-4431:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/2234
KAFKA-4431: Make consumer heartbeat thread a daemon thread
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-4431
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2234.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 #2234
----
commit 08dbb26c94417872b37c10822fb21621f777dca9
Author: Rajini Sivaram <ra...@googlemail.com>
Date: 2016-12-09T13:57:00Z
KAFKA-4431: Make consumer heartbeat thread a daemon thread
----
> 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)