[
https://issues.apache.org/jira/browse/HBASE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-4128:
--------------------------
Description:
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.
was:
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.
Summary: Detect whether there was zookeeper ensemble, master or region
server hanging from previous build (was: Detect whether there was zookeeper
ensemble hanging from previous build)
> 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
