Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <894394932.1229561324456.JavaMail.jira@brutus>
Date: Wed, 17 Dec 2008 16:48:44 -0800 (PST)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4910) NameNode should exclude corrupt
 replicas when choosing excessive replicas to delete
In-Reply-To: <6466516.1229561324444.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.