Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 7 Oct 2015 01:30:26 +0000 (UTC)
From: "Tsz Wo Nicholas Sze (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12902877.1444181390000.42090.1444181426811@Atlassian.JIRA>
In-Reply-To: <JIRA.12902877.1444181390000@Atlassian.JIRA>
References: <JIRA.12902877.1444181390000@Atlassian.JIRA>
 <JIRA.12902877.1444181390476@arcas>
Subject: [jira] [Created] (HDFS-9205) Do not sehedule corrupted blocks for
 replication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tsz Wo Nicholas Sze created HDFS-9205:
-----------------------------------------

             Summary: Do not sehedule corrupted blocks for replication
                 Key: HDFS-9205
                 URL: https://issues.apache.org/jira/browse/HDFS-9205
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
            Reporter: Tsz Wo Nicholas Sze
            Assignee: Tsz Wo Nicholas Sze
            Priority: Minor


Corrupted blocks by definition are blocks cannot be read. As a consequence, they cannot be replicated.  In UnderReplicatedBlocks, there is a queue for QUEUE_WITH_CORRUPT_BLOCKS and chooseUnderReplicatedBlocks may choose blocks from it.  It seems that scheduling corrupted block for replication is wasting resource and potentially slow down replication for the higher priority blocks.


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