You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2012/10/03 09:56:08 UTC
[jira] [Updated] (HDFS-2434) TestNameNodeMetrics.testCorruptBlock
fails intermittently
[ https://issues.apache.org/jira/browse/HDFS-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jing Zhao updated HDFS-2434:
----------------------------
Attachment: HDFS-2434.001.patch
Based on Kihwal's analysis, can we solve the problem on the CorruptBlocks metric by disabling the heartbeats of datanodes before marking the block as corrupt?
> TestNameNodeMetrics.testCorruptBlock fails intermittently
> ---------------------------------------------------------
>
> Key: HDFS-2434
> URL: https://issues.apache.org/jira/browse/HDFS-2434
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Reporter: Uma Maheswara Rao G
> Attachments: HDFS-2434.001.patch
>
>
> java.lang.AssertionError: Bad value for metric CorruptBlocks expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:91)
> at org.junit.Assert.failNotEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:126)
> at org.junit.Assert.assertEquals(Assert.java:470)
> at org.apache.hadoop.test.MetricsAsserts.assertGauge(MetricsAsserts.java:185)
> at org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics.__CLR3_0_2t8sh531i1k(TestNameNodeMetrics.java:175)
> at org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics.testCorruptBlock(TestNameNodeMetrics.java:164)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira