Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 18 Dec 2015 22:03:46 +0000 (UTC)
From: "Chang Li (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12888600.1442593468000.72356.1450476226817@Atlassian.JIRA>
In-Reply-To: <JIRA.12888600.1442593468000@Atlassian.JIRA>
References: <JIRA.12888600.1442593468000@Atlassian.JIRA>
 <JIRA.12888600.1442593468675@arcas>
Subject: [jira] [Updated] (HDFS-9105) separate replication config for client
 to create a file or set replication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chang Li updated HDFS-9105:
---------------------------
    Attachment: HDFS-9105.2.patch

added a unit test to test changes in verifyReplication, which is only used by create file and set replication for a file

> separate replication config for client to create a file or set replication
> --------------------------------------------------------------------------
>
>                 Key: HDFS-9105
>                 URL: https://issues.apache.org/jira/browse/HDFS-9105
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: HDFS-9105.2.patch, HDFS-9105.patch
>
>
> one scenario when we want this new config: we want to enforce min replication of value 2, when client try to create a file, it's check against the replication factor of the new config, which is set to 2,  so that client can not create a file of replication of 1. But when client try to close file and there are some datanode failures in the pipeline and only 1 datanode remain, it is checked against old minReplication value, which has value 1, so we will allow client to close the file.


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