[
https://issues.apache.org/jira/browse/HDFS-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763763#comment-13763763
]
Suresh Srinivas commented on HDFS-3564:
---------------------------------------
bq. This assumes there will be an Apache Hadoop v1 release that supports
Windows, which is presumably the goal for the branch-1-win work?
Right now, there is no such plan, speaking from folks who did all of the
windows work.
BTW the only requirement we have is branch-1 changes must go to trunk first.
There is no such requirement for feature branches. Also there is no more work
planned on branch-trunk-win. All the windows work is now happening on trunk
itself. When we have time, we may push this change to trunk. If you need this,
feel free to post a trunk patch.
> 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
