[
https://issues.apache.org/jira/browse/HDFS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HDFS-875:
-------------------------------
Priority: Blocker (was: Major)
> NameNode incorretly handles corrupt replicas
> --------------------------------------------
>
> Key: HDFS-875
> URL: https://issues.apache.org/jira/browse/HDFS-875
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Hairong Kuang
> Priority: Blocker
> Fix For: 0.21.0, 0.22.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
