[
https://issues.apache.org/jira/browse/HDFS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068861#comment-14068861
]
Allen Wittenauer commented on HDFS-166:
---------------------------------------
Ping!
I bet this has been fixed.
> NameNode#invalidateBlock's requirement on more than 1 valid replica exists
> before scheduling a replica to delete is too strict
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-166
> URL: https://issues.apache.org/jira/browse/HDFS-166
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Hairong Kuang
>
> Currently invalideBlock does not allow to delete a replica only if at least
> two valid replicas exist before deletion is scheduled. This is too
> restrictive if the replica to delete is a corrupt one. NameNode could delete
> a corrupt replica as long as at least one copy (no matter valid or corrupt)
> will be left.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
