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

Bharat Viswanadham edited comment on HDFS-13222 at 3/3/18 12:13 AM:
--------------------------------------------------------------------

[~shv]

It is not really removing a parameter, as it was used in the namenode end, i 
have removed that part of code in balancer. (As the parameter is being used in 
namenode end)

Now, as [~szetszwo] suggested I am updating getBlocks to take an additional 
parameter minBlockSize.


was (Author: bharatviswa):
[~shv]

It is not really removing a parameter, as it was used in the namenode end, i 
have removed that part of code in balancer.

Now, as [~szetszwo] suggested I am updating getBlocks to take an additional 
parameter minBlockSize.

> Remove checking size of block size is less than minblocksize
> ------------------------------------------------------------
>
>                 Key: HDFS-13222
>                 URL: https://issues.apache.org/jira/browse/HDFS-13222
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer & mover
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Minor
>         Attachments: HDFS-13222.00.patch
>
>
> We can remove the check for getBlock().getNumBytes() < getBlocksMinBlockSize
> As this is taken care in the namenode, when it returns blocks, it uses the 
> dfs.balancer.getBlocks.min-block-size and returns blocks greater than 
> minblock size.
>  
> getBlocks Using balancer parameter is done in this Jira HDFS-9412
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to