Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 178E8179E3 for ; Fri, 15 May 2015 15:07:02 +0000 (UTC) Received: (qmail 82606 invoked by uid 500); 15 May 2015 15:07:01 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 82540 invoked by uid 500); 15 May 2015 15:07:01 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 82262 invoked by uid 99); 15 May 2015 15:07:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 May 2015 15:07:00 +0000 Date: Fri, 15 May 2015 15:07:00 +0000 (UTC) From: "Nathan Roberts (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts updated HDFS-8404: --------------------------------- Status: Patch Available (was: Open) > 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.7.0, 2.6.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)