hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mit Desai (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-5836) TestHASafeMode#testBlocksAddedWhenStandbyIsDown fails intermittently on Branch2
Date Mon, 27 Jan 2014 16:36:38 GMT
Mit Desai created HDFS-5836:
-------------------------------

             Summary: TestHASafeMode#testBlocksAddedWhenStandbyIsDown fails intermittently
on Branch2
                 Key: HDFS-5836
                 URL: https://issues.apache.org/jira/browse/HDFS-5836
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.2.0
            Reporter: Mit Desai


This is an intermittent failure. Seems like a JDK7 issue. I did some initial research and
found that the test always fails when it runs the following tests in order.
{noformat}
	  testBlocksRemovedBeforeStandbyRestart
	  testSafeBlockTracking
	  testBlocksAddedWhileStandbyIsDown
{noformat}

The test fails with the following error

{noformat}
Running org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.115 sec <<< FAILURE!
test(org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode)  Time elapsed: 19802 sec  <<<
FAILURE!
java.lang.AssertionError: Bad safemode status: 'Safe mode is ON. The reported blocks 21 has
reached the threshold 0.9990 of total blocks 21. The number of live datanodes 3 has reached
the minimum number 0. Safe mode will be turned off automatically in 28 seconds.'
	at org.junit.Assert.fail(Assert.java:93)
	at org.junit.Assert.assertTrue(Assert.java:43)
	at org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode.assertSafeMode(TestHASafeMode.java:493)
	at org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode.testBlocksAddedWhileStandbyIsDown(TestHASafeMode.java:660)
	at org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode.test(TestHASafeMode.java:120)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


Results :

Failed tests:   test(org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode): Bad safemode
status: 'Safe mode is ON. The reported blocks 21 has reached the threshold 0.9990 of total
blocks 21. The number of live datanodes 3 has reached the minimum number 0. Safe mode will
be turned off automatically in 28 seconds.'
{noformat}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message