NameNode#invalidateBlock's requirement on more than 1 valid replica exists
before scheduling a replica to delete is too strict
------------------------------------------------------------------------------------------------------------------------------
Key: HADOOP-4911
URL: https://issues.apache.org/jira/browse/HADOOP-4911
Project: Hadoop Core
Issue Type: Bug
Components: dfs
Affects Versions: 0.18.3
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.