Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 24 Apr 2015 08:35:39 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12749966.1414028571000.15984.1429864539493@Atlassian.JIRA>
In-Reply-To: <JIRA.12749966.1414028571000@Atlassian.JIRA>
References: <JIRA.12749966.1414028571000@Atlassian.JIRA>
 <JIRA.12749966.1414028571805@arcas>
Subject: [jira] [Updated] (HDFS-7281) Missing block is marked as corrupted
 block
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer updated HDFS-7281:
-----------------------------------
    Hadoop Flags: Incompatible change

Yes, output changes to command lines tools are definitely incompatible changes.  This is covered in http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/Compatibility.html#Command_Line_Interface_CLI .

> Missing block is marked as corrupted block
> ------------------------------------------
>
>                 Key: HDFS-7281
>                 URL: https://issues.apache.org/jira/browse/HDFS-7281
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>              Labels: supportability
>         Attachments: HDFS-7281-2.patch, HDFS-7281-3.patch, HDFS-7281-4.patch, HDFS-7281.patch
>
>
> In the situation where the block lost all its replicas, fsck shows the block is missing as well as corrupted. Perhaps it is better not to mark the block corrupted in this case. The reason it is marked as corrupted is numCorruptNodes == numNodes == 0 in the following code.
> {noformat}
> BlockManager
>     final boolean isCorrupt = numCorruptNodes == numNodes;
> {noformat}
> Would like to clarify if it is the intent to mark missing block as corrupted or it is just a bug.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)