[
https://issues.apache.org/jira/browse/HDFS-10499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622404#comment-15622404
]
Yiqun Lin commented on HDFS-10499:
----------------------------------
Hi [~anu], I am ready to work on this. I have looked into this, I think one
reason is that sometimes the block report haven't been reported to namenode and
then the value {{BytesWithFutureGenerationStamps}} of future block will be 0.
The line {{waitTil(TimeUnit.SECONDS.toMillis(SCAN_WAIT));}} can't gurantee
that. Let me know if you are also working on this, Thanks!
> Intermittent test failure
> org.apache.hadoop.hdfs.server.namenode.TestNameNodeMetadataConsistency.testGenerationStampInFuture
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-10499
> URL: https://issues.apache.org/jira/browse/HDFS-10499
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode, test
> Affects Versions: 3.0.0-alpha1
> Reporter: Hanisha Koneru
> Assignee: Anu Engineer
>
> Per https://builds.apache.org/job/PreCommit-HDFS-Build/15646/testReport/, we
> had the following failure. Local rerun is successful.
> Stack Trace:
> {panel}
> java.lang.AssertionError: expected:<17> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.hdfs.server.namenode.TestNameNodeMetadataConsistency.testGenerationStampInFuture(TestNameNodeMetadataConsistency.java:113)
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
