[
https://issues.apache.org/jira/browse/HDFS-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Yiqun updated HDFS-9375:
----------------------------
Attachment: HDFS-9375.002.patch
Thanks [~brahmareddy] suggestions. I change the usage of exist
setBalancerBandwidth command.{{[-setBalancerBandwidth <bandwidth>
<datanode_host1,...>]}}
1.if the param datanode_host is null,its function is the same as before, is
setting for every node.
2.if the detained_host has one or more hostname values with separator "," ,it
will set bandwidth for these specific nodes.
I update the patch.
> Set balancer bandwidth for specific node
> ----------------------------------------
>
> Key: HDFS-9375
> URL: https://issues.apache.org/jira/browse/HDFS-9375
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Affects Versions: 2.7.1
> Reporter: Lin Yiqun
> Assignee: Lin Yiqun
> Attachments: HDFS-9375.001.patch, HDFS-9375.002.patch
>
>
> Now even though the balancer is impove a lot, but In some cases that is still
> slow. For example when the cluster is extended,the new nodes all need
> balancer datas from existed nodes.In order to improve the balancer
> velocity,generally,we will use {{setBalancerBandwidth}} of {{dfsadmin}}
> command.But this is set for every node, obviously,we can increase more
> bandwidth for new nodes because these nodes lacking of data.When the new
> nodes balancer data enough,we can let new nodes to work.So we can define a
> new clientDatanode interface to set specific node's bandwidth.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
