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

Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/05/05 20:13:13 UTC

[jira] [Resolved] (KAFKA-3581) Use timeout when joining threads in system test services

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

Ewen Cheslack-Postava resolved KAFKA-3581.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.0.0
                   0.10.1.0

Issue resolved by pull request 1297
[https://github.com/apache/kafka/pull/1297]

> Use timeout when joining threads in system test services
> --------------------------------------------------------
>
>                 Key: KAFKA-3581
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3581
>             Project: Kafka
>          Issue Type: Bug
>          Components: system tests
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.10.1.0, 0.10.0.0
>
>
> We have several instances in our system test services where we invoke Thread.join() in the stop_node() function to stop the service. It probably makes sense to use a timeout in join() to ensure that the process eventually has a chance to do unclean shutdown when the process becomes unresponsive. We have seen several cases in our daily runs (with the verifiable consumer in particular) where the process seems to hang on this join.



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