[
https://issues.apache.org/jira/browse/HDFS-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945497#comment-14945497
]
Mingliang Liu commented on HDFS-9199:
-------------------------------------
# The name {{dfs.namenode.replication.min}} was chosen deliberately.
{{dfs.namenode.replication.min}} was designed to replace the
{{dfs.replication.min}} config key in {{HdfsConfiguration.java}}
{code}
118 new DeprecationDelta("dfs.replication.min",
119 DFSConfigKeys.DFS_NAMENODE_REPLICATION_MIN_KEY),
{code}
For this reason, the {{dfs.namenode.replication.min}} is preferred to
{{dfs.replication.min}}.
# Though both of the {{dfs.namenode.replication.min}} and
{{dfs.replication.max}} are for replication numbers threshold, they are used in
different scenarios. {{dfs.replication.max}} is like a general purpose
whole-system maximum replication hard limit, while the
{{dfs.namenode.replication.min}} is to check how many minimum copies are
needed, or else write is disallowed. The latter is valid only in namenode scope
so the _namenode_ prefix is just fine.
For those two reasons, I think we don't need to rename
{{dfs.namenode.replication.min}} to {{dfs.replication.min}}.
> rename dfs.namenode.replication.min to dfs.replication.min
> ----------------------------------------------------------
>
> Key: HDFS-9199
> URL: https://issues.apache.org/jira/browse/HDFS-9199
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Allen Wittenauer
> Assignee: Mingliang Liu
>
> dfs.namenode.replication.min should be dfs.replication.min to match the other
> dfs.replication config knobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
