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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/07/23 06:43:09 UTC

[jira] [Commented] (HBASE-4128) Detect whether there was zookeeper ensemble hanging from previous build

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

stack commented on HBASE-4128:
------------------------------

Our 0.90 build was using 'ubuntu' as host to build on.  This could be more than one machine.  I changed it to be 'ubuntu2'.  I also have the 0.90 build first run some shell commands -- hostname, ulimit -a, and jps.  We can see if any zk running.   

> Detect whether there was zookeeper ensemble 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 hanging from previous build.
> We should detect (and terminate, if possible) the hanging zk ensemble from previous build as the first step in current build.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira