[ 
https://issues.apache.org/jira/browse/HDFS-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079835#comment-13079835
 ] 

Hudson commented on HDFS-2202:
------------------------------

Integrated in Hadoop-Hdfs-trunk #738 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/738/])
    HDFS-2202. Add a new DFSAdmin command to set balancer bandwidth of 
datanodes without restarting.  Contributed by Eric Payne

szetszwo : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1152401
Files : 
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/TestBalancerBandwidth.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/protocol/BalancerBandwidthCommand.java
* /hadoop/common/trunk/hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/DistributedFileSystem.java
* /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/DFSClient.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/protocol/ClientProtocol.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeManager.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeDescriptor.java
* /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/tools/DFSAdmin.java
* 
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/protocol/DatanodeProtocol.java


> Changes to balancer bandwidth should not require datanode restart.
> ------------------------------------------------------------------
>
>                 Key: HDFS-2202
>                 URL: https://issues.apache.org/jira/browse/HDFS-2202
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: balancer, data-node
>    Affects Versions: 0.20.205.0, 0.23.0
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>             Fix For: 0.20.205.0, 0.23.0
>
>         Attachments: HDFS-2171.patch, HDFS-2202.0.20.205.0.v1.patch, 
> HDFS-2202.0.20.205.0.v2.patch, HDFS-2202.0.23.0.v1.patch, 
> HDFS-2202.0.23.0.v2.patch, HDFS-2202.patch, ant.test.0.23.out
>
>
> Currently in order to change the value of the balancer bandwidth 
> (dfs.datanode.balance.bandwidthPerSec), the datanode daemon must be restarted.
> The optimal value of the bandwidthPerSec parameter is not always (almost 
> never) known at the time of cluster startup, but only once a new node is 
> placed in the cluster and balancing is begun. If the balancing is taking too 
> long (bandwidthPerSec is too low) or the balancing is taking up too much 
> bandwidth (bandwidthPerSec is too high), the cluster must go into a 
> "maintenance window" where it is unusable while all of the datanodes are 
> bounced. In large clusters of thousands of nodes, this can be a real 
> maintenance problem because these "mainenance windows" can take a long time 
> and there may have to be several of them while the bandwidthPerSec is 
> experimented with and tuned.
> A possible solution to this problem would be to add a -bandwidth parameter to 
> the balancer tool. If bandwidth is supplied, pass the value to the datanodes 
> via the OP_REPLACE_BLOCK and OP_COPY_BLOCK DataTransferProtocol requests. 
> This would make it necessary, however, to change the DataTransferProtocol 
> version.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to