Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 21 Oct 2016 22:52:58 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12965249.1462447040000.57111.1477090378543@Atlassian.JIRA>
In-Reply-To: <JIRA.12965249.1462447040000@Atlassian.JIRA>
References: <JIRA.12965249.1462447040000@Atlassian.JIRA> <JIRA.12965249.1462447040776@arcas>
Subject: [jira] [Commented] (HDFS-10368) Erasure Coding: Deprecate
 replication-related config keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 21 Oct 2016 22:53:00 -0000


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

Andrew Wang commented on HDFS-10368:
------------------------------------

Thanks for the investigation Rakesh. I think there's little harm in adding deprecations, since the old keys will keep on working.

Some of these seem like a simple rename+deprecation which we can handle here:

* dfs.namenode.replication.considerLoad
* dfs.namenode.replication.considerLoad.factor
* dfs.namenode.replication.interval

Some of these we should leave:

* dfs.namenode.replication.min - I assume this only applies to replicated blocks, not striped?
* The various safemode / maintenance mode replication thresholds, I assume there is different handling for striped blocks?

Some seem like they need to be reworked since they no longer do what is advertised, since EC reconstruction involves reading multiple blocks:

* dfs.namenode.replication.work.multiplier.per.iteration
* dfs.namenode.replication.max-streams
* dfs.namenode.replication.max-streams-hard-limit

These last three will hopefully be addressed by HDFS-11023.

> Erasure Coding: Deprecate replication-related config keys
> ---------------------------------------------------------
>
>                 Key: HDFS-10368
>                 URL: https://issues.apache.org/jira/browse/HDFS-10368
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: erasure-coding
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>              Labels: hdfs-ec-3.0-must-do
>
> This jira is to visit the replication based config keys and deprecate them(if necessary) in order to make it more meaningful.
> Please refer [discussion thread|https://issues.apache.org/jira/browse/HDFS-9869?focusedCommentId=15249363&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15249363]


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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org