[HBASE-14678] Experiment: Temporarily disable balancer and a few others to see if root of crashed/timedout JVMs

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.2.0, 1.3.0, 2.0.0
• Component/s: test
• Assignee: Phil Yang
• Reporter: Michael Stack
• Created: 22/Oct/15 19:07
• Updated: 23/Mar/16 21:50
• Resolved: 23/Mar/16 21:42

Description

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.

Issue Links

• is related to: HBASE-14589 Looking for the surefire-killer; builds being killed...ExecutionException: java.lang.RuntimeException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
• relates to: HBASE-14701 Fix flakey Failed tests: TestMobFlushSnapshotFromClient>TestFlushSnapshotFromClient.testSkipFlushTableSnapshot:199 null

Sub-Tasks

• Reenable TestShell and TestStochasticLoadBalancer: Resolved