Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Fri, 2 May 2014 20:40:15 +0000 (UTC)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12712035.1399063102642.222570.1399063215044@arcas>
In-Reply-To: <JIRA.12712035.1399063102642@arcas>
References: <JIRA.12712035.1399063102642@arcas>
Subject: [jira] [Created] (HDFS-6325) Append should fail if the last block
 has unsufficient number of replicas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Konstantin Shvachko created HDFS-6325:
-----------------------------------------

             Summary: Append should fail if the last block has unsufficient number of replicas
                 Key: HDFS-6325
                 URL: https://issues.apache.org/jira/browse/HDFS-6325
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 2.2.0
            Reporter: Konstantin Shvachko
             Fix For: 2.5.0


Currently append() succeeds on a file with the last block that has no replicas. But the subsequent updatePipeline() fails as there are no replicas with the exception "Unable to retrieve blocks locations for last block". This leaves the file unclosed, and others can not do anything with it until its lease expires.
The solution is to check replicas of the last block on the NameNode and fail during append() rather than during updatePipeline().
How many replicas should be present before NN allows to append? I see two options:
# min-replication: allow append if the last block is minimally replicated (1 by default)
# full-replication: allow append if the last block is fully replicated (3 by default)


--
This message was sent by Atlassian JIRA
(v6.2#6252)