[
https://issues.apache.org/jira/browse/HDFS-14560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863603#comment-16863603
]
Hudson commented on HDFS-14560:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16743 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16743/])
HDFS-14560. Allow block replication parameters to be refreshable. (inigoiri:
rev 4f455290b15902e7e44c4b1a762bf915414b2bb6)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* (add)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestRefreshNamenodeReplicationConfig.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/tools/TestDFSAdmin.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
> Allow block replication parameters to be refreshable
> ----------------------------------------------------
>
> Key: HDFS-14560
> URL: https://issues.apache.org/jira/browse/HDFS-14560
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.3.0
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Fix For: 3.3.0, 3.2.1, 3.1.3
>
> Attachments: HDFS-14560.001.patch, HDFS-14560.002.patch,
> HDFS-14560.003.patch, HDFS-14560.004.patch, HDFS-14560.005.patch,
> HDFS-14560.branch-3.1.patch
>
>
> There are 3 key parameters that control the speed of block replication across
> the cluster:
> {code}
> dfs.namenode.replication.max-streams
> dfs.namenode.replication.max-streams-hard-limit
> dfs.namenode.replication.work.multiplier.per.iteration
> {code}
> These are used when decomissioning nodes and when under replicated blocks are
> being recovered across the cluster. There are times when it may be desirable
> to increase the speed of replication and then reduce it again (eg during off
> peak hours) without restarting the namenode.
> Therefore it would be good to be able to reconfigure / refresh these
> parameters dynamically without a namenode restart.
> This Jira is to allow these parameters to be refreshed at runtime without a
> restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
