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

Tsz Wo Nicholas Sze commented on HDFS-13222:
--------------------------------------------

The conf dfs.balancer.getBlocks.min-block-size is a Balancer conf.  HDFS-9412 
makes NN using it.  There are two ways to fix it
# Change NN to ignore it from NN conf.  Pass the Balancer conf value from 
Balancer to NN via getBlocks in each RPC.
# Keep NN reading it if it is set in NN conf.  Pass the Balancer conf value 
from Balancer to NN via getBlocks in each RPC.  Use the min value from both 
confs.

It seems that #1 is good enough.  The only bad thing is that user may have set 
it in NN conf but not Balancer conf.  Not a big deal.  Just kill the Balancer 
and fix the conf.

> 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