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

Bharat Viswanadham edited comment on HDFS-13222 at 3/27/18 2:00 AM:
--------------------------------------------------------------------

Hi [~shv]

If Balancer is upgraded after namenode, balancer discards the blocksize which 
are less than minBlockSize in the old balancer. So, from behavior end, it will 
not be an issue, but NN will send the blocks unnecessarily to balancer with 
size greater than zero (If balancer is upgraded later).

 

Let me know if you still want to fix the issue or if I am missing something 
here, I can open a follow-up up jira.

 


was (Author: bharatviswa):
Hi [~shv]

If Balancer is not upgraded, balancer discards the blocksize which are less 
than minBlockSize in the old balancer. So, from behavior end, it will not be an 
issue, but NN will send the blocks unnecessarily to balancer with size greater 
than zero (If balancer is upgraded later).

 

Let me know if you still want to fix the issue or if I am missing something 
here, I can open a follow-up up jira.

 

> Update getBlocks method to take minBlockSize in RPC calls
> ---------------------------------------------------------
>
>                 Key: HDFS-13222
>                 URL: https://issues.apache.org/jira/browse/HDFS-13222
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: balancer & mover
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>             Fix For: 3.1.0
>
>         Attachments: HDFS-13222.00.patch, HDFS-13222.01.patch, 
> HDFS-13222.02.patch
>
>
>  
> getBlocks Using balancer parameter is done in this Jira HDFS-9412
>  
> Pass the Balancer conf value from Balancer to NN via getBlocks in each RPC. 
> as [~szetszwo] suggested
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to