[ 
https://issues.apache.org/jira/browse/HDFS-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512770#comment-16512770
 ] 

Íñigo Goiri commented on HDFS-6126:
-----------------------------------

We are seeing this error once in a while.
For example 
[here|https://builds.apache.org/job/PreCommit-HDFS-Build/24436/testReport/org.apache.hadoop.hdfs.server.namenode.metrics/TestNameNodeMetrics/testCorruptBlock/].
There are many JIRAs that have targetted this: HDFS-2434, HDFS-3812, HDFS-4338, 
HDFS-4355.
However, this is still present.
[~zuzhan], can you take a look?

> TestnameNodeMetrics#testCorruptBlock fails intermittently
> ---------------------------------------------------------
>
>                 Key: HDFS-6126
>                 URL: https://issues.apache.org/jira/browse/HDFS-6126
>             Project: Hadoop HDFS
>          Issue Type: Test
>    Affects Versions: 2.4.0
>            Reporter: Mit Desai
>            Priority: Major
>
> I get the following error
> {noformat}
> testCorruptBlock(org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics)
>   Time elapsed: 5.556 sec  <<< FAILURE!
> java.lang.AssertionError: Bad value for metric CorruptBlocks expected:<1> but 
> was:<0>
>       at org.junit.Assert.fail(Assert.java:93)
>       at org.junit.Assert.failNotEquals(Assert.java:647)
>       at org.junit.Assert.assertEquals(Assert.java:128)
>       at org.junit.Assert.assertEquals(Assert.java:472)
>       at 
> org.apache.hadoop.test.MetricsAsserts.assertGauge(MetricsAsserts.java:190)
>       at 
> org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics.testCorruptBlock(TestNameNodeMetrics.java:247)
> Results :
> Failed tests: 
>   TestNameNodeMetrics.testCorruptBlock:247 Bad value for metric CorruptBlocks 
> expected:<1> but was:<0>
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to