[
https://issues.apache.org/jira/browse/HDFS-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812430#comment-13812430
]
Tsz Wo (Nicholas), SZE commented on HDFS-5452:
----------------------------------------------
Just checked TestReplicationPolicy. It did not fail in my machine. Not sure
why it still fails in your case.
{noformat}
Running org.apache.hadoop.hdfs.server.blockmanagement.TestReplicationPolicy
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.514 sec -
in org.apache.hadoop.hdfs.server.blockmanagement.TestReplicationPolicy
Results :
Tests run: 24, Failures: 0, Errors: 0, Skipped: 0
{noformat}
> Fix TestReplicationPolicy and TestBlocksScheduledCounter
> --------------------------------------------------------
>
> Key: HDFS-5452
> URL: https://issues.apache.org/jira/browse/HDFS-5452
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: h5452_20131101.patch
>
>
> TestReplicationPolicy: the log level checking is incorrect.
> TestBlocksScheduledCounter: HDFS-5222, which moved block schedule information
> from DatanodeDescriptor to DatanodeStorageInfo, is incorrect since a replica
> scheduled to a storage may eventually be written to another storage in the
> same datanode.
--
This message was sent by Atlassian JIRA
(v6.1#6144)