[
https://issues.apache.org/jira/browse/HDFS-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198021#comment-15198021
]
Yongjun Zhang commented on HDFS-9940:
-------------------------------------
Hi [~szetszwo],
Thanks for your comment.
Per the current implementation of {{public String
reconfigurePropertyImpl(String property, String newVal)}},
{{DFS_DATANODE_BALANCE_MAX_NUM_CONCURRENT_MOVES_KEY}} is allowed to reconfigure
without restarting DN.
Agree?
About abusing the cluster by Balancer, the balancer can only be run as admin
user "hdfs", right?
What about having two configurations as I proposed in my last comment? This
will address your concern of abuse too hopefully.
Thanks.
> Rename dfs.balancer.max.concurrent.moves to avoid confusion
> -----------------------------------------------------------
>
> Key: HDFS-9940
> URL: https://issues.apache.org/jira/browse/HDFS-9940
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Affects Versions: 2.6.0
> Reporter: John Zhuge
> Assignee: John Zhuge
> Priority: Minor
> Labels: supportability
> Fix For: 2.8.0
>
>
> It is very confusing for both Balancer and Datanode to use the same property
> {{dfs.datanode.balance.max.concurrent.moves}}. It is especially so for the
> Balancer because the property has "datanode" in the name string. Many
> customers forget to set the property for the Balancer.
> Change the Balancer to use a new property
> {{dfs.balancer.max.concurrent.moves}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
