[
https://issues.apache.org/jira/browse/HDFS-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197652#comment-15197652
]
Yongjun Zhang commented on HDFS-9940:
-------------------------------------
Hi [~jzhuge],
I like 2) too. Thanks for bringing to our attention of HDFS-7466, and here is
what I think we could address it.
We can have two config properties
* {{dfs.balancer.max.concurrent.moves}}, which is a rename of
{{dfs.datanode.balance.max.concurrent.moves}} (current default 5), and is used
for global setting, and this what we discussed above.
* {{dfs.datanode.max.concurrent.moves}}, which can be set per datanode to
address HDFS-7466. Default it to {{-1}};
Solution:
* Datanode will take the value of {{dfs.datanode.max.concurrent.moves}} , if
its value is not -1. However, if its value is -1, then take the value from
{{dfs.balancer.max.concurrent.moves}} set from approach 2.
This way, we address both the issue here (rename the config, plus only need to
set at balancer command line), and the issue reported in HDFS-7466.
HI [~szetszwo], [~qwertymaniac] and [~jzhuge], what do you think?
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)
