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

Suresh Srinivas commented on HDFS-3564:
---------------------------------------

bq. Looks like this change went in branch-1-win but not trunk or branch-1. Why 
is that? This means the Windows code base is diverging from the other 
platforms, preventing this is why changes are supposed to go through trunk 
first. IMO this needs to be done in trunk or we should revert this change.

branch-1-win is for feature development. When and if it goes in to branch-1, 
before that it will also go into trunk. I am not sure why a change from 
branch-1-win must go into trunk or branch-1.
                
> Design enhancements to the pluggable blockplacementpolicy
> ---------------------------------------------------------
>
>                 Key: HDFS-3564
>                 URL: https://issues.apache.org/jira/browse/HDFS-3564
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Sumadhur Reddy Bolli
>            Assignee: Sumadhur Reddy Bolli
>             Fix For: 1-win
>
>         Attachments: blockPlacementPolicy enhancements.pdf, 
> policyenhancements-branch-1-win.patch
>
>
> Currently, it is assumed that no placement policy other than the default can 
> work with the balancer and that the minimum racks required for any placement 
> policy is always 2. The attached pdf suggests enhancements to the existing 
> block placement policy abstraction to enable the following
> a) Let placement policies decide if they are compatible with balancer
> b) Provide an api to move blocks for balancing
> c) Let the placement policy decide the minimum number of racks given the 
> replication factor
> d) Also, the private methods in the default policy are made protected, 
> similar to the way its done in trunk, to enable easy derivation of custom 
> policies.
> Please refer the pdf and the patch for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to