[
https://issues.apache.org/jira/browse/HDFS-14940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977763#comment-16977763
]
Surendra Singh Lilhore commented on HDFS-14940:
-----------------------------------------------
{quote}Shouldn't we have it at Namenode side too, as you said before and we can
have it at the client side too saving the RPC.
{quote}
Why to add same condition in two place, lets add it in server only then if you
are ok which extra RPC.
Keeping same condition in two place is not good. If in future some one change
one place and forgot the change other place can cause behaviour change.
> HDFS Balancer : Do not allow to set balancer maximum network bandwidth more
> than 1TB
> ------------------------------------------------------------------------------------
>
> Key: HDFS-14940
> URL: https://issues.apache.org/jira/browse/HDFS-14940
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer & mover
> Affects Versions: 3.1.1
> Environment: 3 Node HA Setup
> Reporter: Souryakanta Dwivedy
> Priority: Minor
> Attachments: BalancerBW.PNG, HDFS-14940.001.patch,
> HDFS-14940.002.patch, HDFS-14940.003.patch
>
>
> HDFS Balancer : getBalancerBandwidth displaying wrong values for the maximum
> network bandwidth used by the datanode
> while network bandwidth set with values as 1048576000g/1048p/1e
> Steps :-
> * Set balancer bandwith with command setBalancerBandwidth and vlaues as
> [1048576000g/1048p/1e]
> * - Check bandwidth used by the datanode during HDFS block balancing with
> command :hdfs dfsadmin -getBalancerBandwidth " check it will display some
> different values not the same value as set
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
