[
https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masatake Iwasaki updated HDFS-9358:
-----------------------------------
Attachment: HDFS-9358.001.patch
Thanks for reporting this, [~jojochuang].
The testNodeCount expects number of excess replica to be increased to 2 by
excessReplicateMap. (live, excess) could be changed in the case as
{noformat}
(live, excess): (3, 1) -> (2, 2)
{noformat}
If invalidation of existing excess replica is executed before
excessReplicateMap is updated, number of excess replica never be 2.
{noformat}
(live, excess): (3, 1) -> (3, 0) -> (2, 1)
{noformat}
Attached 001 fix the test to wait for invalidation of the 1st excess replica
then check the 2nd excess replica is detected.
> TestNodeCount#testNodeCount timed out
> -------------------------------------
>
> Key: HDFS-9358
> URL: https://issues.apache.org/jira/browse/HDFS-9358
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Wei-Chiu Chuang
> Assignee: Masatake Iwasaki
> Attachments: HDFS-9358.001.patch
>
>
> I have seen this test failure occurred a few times in trunk:
> Error Message
> Timeout: excess replica count not equal to 2 for block blk_1073741825_1001
> after 20000 msec. Last counts: live = 2, excess = 0, corrupt = 0
> Stacktrace
> java.util.concurrent.TimeoutException: Timeout: excess replica count not
> equal to 2 for block blk_1073741825_1001 after 20000 msec. Last counts: live
> = 2, excess = 0, corrupt = 0
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
