Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 26 Mar 2015 03:04:57 +0000 (UTC)
From: "Ming Ma (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12785767.1427339077000.32428.1427339097811@Atlassian.JIRA>
In-Reply-To: <JIRA.12785767.1427339077000@Atlassian.JIRA>
References: <JIRA.12785767.1427339077000@Atlassian.JIRA>
 <JIRA.12785767.1427339077514@arcas>
Subject: [jira] [Created] (HDFS-7993) Incorrect descriptions in fsck when
 nodes are decommissioned
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ming Ma created HDFS-7993:
-----------------------------

             Summary: Incorrect descriptions in fsck when nodes are decommissioned
                 Key: HDFS-7993
                 URL: https://issues.apache.org/jira/browse/HDFS-7993
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Ming Ma


When you run fsck with "-files" or "-racks", you will get something like below if one of the replicas is decommissioned.

{noformat}
blk_x len=y repl=3 [dn1, dn2, dn3, dn4]
{noformat}

That is because in NamenodeFsck,, the repl count comes from live replicas count; while the actual nodes come from LocatedBlock which include decommissioned nodes.

Another issue in NamenodeFsck is BlockPlacementPolicy's verifyBlockPlacement verifies LocatedBlock that includes decommissioned nodes. However, it seems better to exclude the decommissioned nodes in the verification; just like how fsck excludes decommissioned nodes when it check for under replicated blocks.


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