Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 25 Jun 2013 09:26:23 +0000 (UTC)
From: "Fengdong Yu (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12465184.1274509229369.170579.1372152383634@arcas>
In-Reply-To: <JIRA.12465184.1274509229369@arcas>
References: <JIRA.12465184.1274509229369@arcas>
Subject: [jira] [Commented] (HDFS-1172) Blocks in newly completed files are
 considered under-replicated too quickly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Fengdong Yu commented on HDFS-1172:
-----------------------------------

bq. This litters the task logs with the NotReplicatedYetException

This does look like client require a new block before the previous block pipeline is not finished.
                
> Blocks in newly completed files are considered under-replicated too quickly
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-1172
>                 URL: https://issues.apache.org/jira/browse/HDFS-1172
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.21.0
>            Reporter: Todd Lipcon
>             Fix For: 0.24.0
>
>         Attachments: HDFS-1172.patch, hdfs-1172.txt, hdfs-1172.txt, replicateBlocksFUC1.patch, replicateBlocksFUC1.patch, replicateBlocksFUC.patch
>
>
> I've seen this for a long time, and imagine it's a known issue, but couldn't find an existing JIRA. It often happens that we see the NN schedule replication on the last block of files very quickly after they're completed, before the other DNs in the pipeline have a chance to report the new block. This results in a lot of extra replication work on the cluster, as we replicate the block and then end up with multiple excess replicas which are very quickly deleted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira