You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2011/02/11 02:36:57 UTC

[jira] Resolved: (HDFS-875) NameNode incorretly handles corrupt replicas

     [ https://issues.apache.org/jira/browse/HDFS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Shvachko resolved HDFS-875.
--------------------------------------

    Resolution: Duplicate

Resolving as duplicate of HDFS-900. Feel free to reopen if there is more work needed.

> 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.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira