hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9205) Do not schedule corrupt blocks for replication
Date Fri, 16 Oct 2015 20:25:05 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961316#comment-14961316
] 

Hudson commented on HDFS-9205:
------------------------------

ABORTED: Integrated in Hadoop-Hdfs-trunk-Java8 #506 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/506/])
Revert "Move HDFS-9205 to trunk in CHANGES.txt." (szetszwo: rev a554701fe4402ae30461e2ef165cb60970a202a0)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> Do not schedule corrupt 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
>             Fix For: 2.8.0
>
>         Attachments: h9205_20151007.patch, h9205_20151007b.patch, h9205_20151008.patch,
h9205_20151009.patch, h9205_20151009b.patch, h9205_20151013.patch, h9205_20151015.patch
>
>
> 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)

Mime
View raw message