You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "nkeywal (Commented) (JIRA)" <ji...@apache.org> on 2011/10/13 13:05:11 UTC

[jira] [Commented] (HBASE-4128) Detect whether there was zookeeper ensemble, master or region server hanging from previous build

    [ https://issues.apache.org/jira/browse/HBASE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126485#comment-13126485 ] 

nkeywal commented on HBASE-4128:
--------------------------------

Note as well that there is a bug in surefire (http://jira.codehaus.org/browse/SUREFIRE-773), and the java processes are not always killed when there is a timeout. So there could be more processes to kill than only the zk.
                
> Detect whether there was zookeeper ensemble, master or region server hanging from previous build
> ------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4128
>                 URL: https://issues.apache.org/jira/browse/HBASE-4128
>             Project: HBase
>          Issue Type: Task
>            Reporter: Ted Yu
>
> Quite often, we see unit test(s) time out after 15 minutes.
> One example was TestShell: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/239/console
> This may be caused by zookeeper ensemble, master or region server hanging from previous build.
> We should detect (and terminate, if possible) the hanging zk ensemble, master or region server from previous build as the first step in current build.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira