[
https://issues.apache.org/jira/browse/HBASE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070062#comment-13070062
]
stack commented on HBASE-4128:
------------------------------
@Eric Yes. We'll now jps as first thing we do before build. Lets see what that
turns up next time we have a TestShell hang. If its hung master/regionserver,
should show... or I suppose it won't really. We'll see the maven surefile
process running but that should be clue enough.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
