[
https://issues.apache.org/jira/browse/HBASE-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979466#comment-14979466
]
Heng Chen commented on HBASE-14678:
-----------------------------------
{quote}
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
Hanging test : org.apache.hadoop.hbase.mapreduce.TestSyncTable
Hanging test : org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles
Hanging test : org.apache.hadoop.hbase.mapreduce.TestTableMapReduce
Printing Failing tests
Failing test : org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient
Failing test : org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient
{quote}
Could you post the console output URL? Thanks [~stack]
> Experiment: Temporarily disable balancer and a few others to see if root of
> crashed/timedout JVMs
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-14678
> URL: https://issues.apache.org/jira/browse/HBASE-14678
> Project: HBase
> Issue Type: Sub-task
> Components: test
> Reporter: stack
>
> Looking at recent builds of 1.2, I see a few of the runs finishing with kills
> and notice that a JVM exited without reporting back state. Running the
> hanging test finder, I can see at least that in one case that the balancer
> tests seem to be outstanding; looking in test output, seems to be still going
> on.... A few others are reported as hung but they look like they have just
> started running and are just killed by surefire.
> This issue is about trying to disable a few of the problematics like balancer
> tests to see if our overall stability improves. If so, I can concentrate on
> stabilizing these few tests. Else will just undo the experiment and put the
> tests back on line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
