[
https://issues.apache.org/jira/browse/HADOOP-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-1456:
------------------------------
Resolution: Fixed
Fix Version/s: 0.14.0
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Dhruba!
> TestDecommission fails with assertion Number of replicas for block1
> expected:<3> but was:<2>
> ---------------------------------------------------------------------------------------------
>
> Key: HADOOP-1456
> URL: https://issues.apache.org/jira/browse/HADOOP-1456
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.14.0
>
> Attachments: testDecommission1456.patch
>
>
> TestDecommission fails sometimes with the following assertion:
> junit.framework.AssertionFailedError: Number of replicas for block1
> expected:<3> but was:<2>
> at
> org.apache.hadoop.dfs.TestDecommission.checkFile(TestDecommission.java:89)
> at
> org.apache.hadoop.dfs.TestDecommission.testDecommission(TestDecommission.java:285)
> More logs here:
> http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/231/testReport/org.apache.hadoop.dfs/TestDecommission/testDecommission/
> This test creates a file with target replication factor of 3. Then it
> verifies that the file actually has a replciation of 3. I think the test
> should set "dfs.replication.considerLoad" to false before starting the test
> so that the namenode ignores the load on datanodes while allocating replicas.
> This is the approach folowed by TestReplication.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
