[
https://issues.apache.org/jira/browse/HDFS-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249363#comment-15249363
]
Zhe Zhang commented on HDFS-9869:
---------------------------------
bq. How about keeping only the recent property name |
dfs.namenode.replication.pending.timeout-sec |
dfs.namenode.reconstruction.pending.timeout-sec |
I was thinking keeping both entries, but making the right hand side of both to
the new config key {{dfs.namenode.reconstruction.pending.timeout-sec}}. Pinging
[~andrew.wang] for thoughts.
bq. As a followup we should also deprecate other replication-related config
keys.
bq. Shall we do this deprecation through another follow-up jira task?
Yes, given the size of this change I think we should do other deprecations in a
separate JIRA.
> Erasure Coding: Rename replication-based names in BlockManager to more
> generic [part-2]
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-9869
> URL: https://issues.apache.org/jira/browse/HDFS-9869
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: erasure-coding
> Reporter: Rakesh R
> Assignee: Rakesh R
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-9869-001.patch, HDFS-9869-002.patch,
> HDFS-9869-003.patch, HDFS-9869-004.patch
>
>
> The idea of this jira is to rename the following entities in BlockManager as,
> - {{PendingReplicationBlocks}} to {{PendingReconstructionBlocks}}
> - {{excessReplicateMap}} to {{extraRedundancyMap}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
