[
https://issues.apache.org/jira/browse/HBASE-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975132#comment-14975132
]
stack commented on HBASE-14678:
-------------------------------
On 1.2, I saw this just now:
Hanging test :
org.apache.hadoop.hbase.mapreduce.TestImportTSVWithOperationAttributes
Hanging test : org.apache.hadoop.hbase.mapreduce.TestTableSnapshotInputFormat
Hanging test : org.apache.hadoop.hbase.mapreduce.TestImportExport
Hanging test : org.apache.hadoop.hbase.mapreduce.TestTableInputFormat
Hanging test :
org.apache.hadoop.hbase.mapreduce.TestImportTSVWithVisibilityLabels
There are kills in the test listing.... 5 kills.
Let me try converting over these MR jobs to run without cluster... backporting
HBASE-14684 rather than disabling the above.
> 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)
