hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4910) NameNode should exclude corrupt replicas when choosing excessive replicas to delete
Date Thu, 18 Dec 2008 00:48:44 GMT

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

Hairong Kuang updated HADOOP-4910:
----------------------------------

          Component/s: dfs
    Affects Version/s: 0.17.0

> NameNode should exclude corrupt replicas when choosing excessive replicas to delete
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-4910
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4910
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.0
>            Reporter: Hairong Kuang
>
> Currently, when NameNode handles an over-replicated block in FSNamesystem#processOverReplicatedBlock,
it excludes ones already in excessReplicateMap and decommissed ones, but it treats a corrupt
replica as a valid one. This may lead to unnecessary deletion of more replicas and thus cause
data lose. It should exclude corrupt replicas as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message