Description
I reviewed how NameNode handles corrupt replicas as part of work on HDFS-145. Comparing to releases prior to 0.21, NameNode now does a good job identifying corrupt replicas, but it seems to me there are two flaws how it handles the corrupt replicas:
1. NameNode does not add corrupt replicas to the block locations as what NameNode does before;
2. If the corruption is caused by generation stamp mismatch or state mismatch, the wrong GS and state do not get put in corruptReplicasMap. Therefore it may lead to the deletion of the wrong replica.
Attachments
Issue Links
- is related to
-
HDFS-900 Corrupt replicas are not tracked correctly through block report from DN
-
- Closed
-