Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 19 May 2015 18:07:00 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12829987.1431639801000.159818.1432058820049@Atlassian.JIRA>
In-Reply-To: <JIRA.12829987.1431639801000@Atlassian.JIRA>
References: <JIRA.12829987.1431639801000@Atlassian.JIRA>
 <JIRA.12829987.1431639801196@arcas>
Subject: [jira] [Commented] (HDFS-8404) Pending block replication can get
 stuck using older genstamp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kihwal Lee commented on HDFS-8404:
----------------------------------

+1 the patch looks good. 

> Pending block replication can get stuck using older genstamp
> ------------------------------------------------------------
>
>                 Key: HDFS-8404
>                 URL: https://issues.apache.org/jira/browse/HDFS-8404
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.6.0, 2.7.0
>            Reporter: Nathan Roberts
>            Assignee: Nathan Roberts
>         Attachments: HDFS-8404-v0.patch, HDFS-8404-v1.patch
>
>
> If an under-replicated block gets into the pending-replication list, but later the  genstamp of that block ends up being newer than the one originally submitted for replication, the block will fail replication until the NN is restarted. 
> It will be safer if processPendingReplications()  gets up-to-date blockinfo before resubmitting replication work.


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