[
https://issues.apache.org/jira/browse/HDFS-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450817#comment-13450817
]
Todd Lipcon commented on HDFS-3902:
-----------------------------------
bq. That assertion seems very odd to me: it claims that a replication=3 block
with two corrupt replicas should report 1 location, but once we corrupt the
third replica the block should report all three (corrupt!) locations.
Oddly enough, this is the expected behavior, AFAIK.
> TestDatanodeBlockScanner is flaky, broke entirely after HDFS-3828
> -----------------------------------------------------------------
>
> Key: HDFS-3902
> URL: https://issues.apache.org/jira/browse/HDFS-3902
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.1.0-alpha
> Reporter: Andy Isaacson
> Assignee: Andy Isaacson
> Priority: Minor
>
> Since HDFS-3828 fixed the block scanner to not repeatedly rescan small
> blockpools, TestDatanodeBlockScanner times out after 13 minutes in
> {{waitReplication}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
