[
https://issues.apache.org/jira/browse/HDFS-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763218#comment-13763218
]
Eli Collins commented on HDFS-3564:
-----------------------------------
In order to keep the v1 and the v2 Windows support compatible changes should go
to branch-trunk-win before branch-1-win, otherwise the v1 Hadoop Windows
release will have features that are not in the current v2 Hadoop releases
(which is incompatible, upgrading to v2 will drop this feature). This assumes
there will be an Apache Hadoop v1 release that supports Windows, which is
presumably the goal for the branch-1-win work?
If the plan is to implement this jira in trunk before doing such a release,
what jira tracks that? This one has been resolved as fixed and it's not covered
by HADOOP-8468.
Also, in general we don't want to do new feature development solely on old
releases branches first, w/o first doing it against trunk, that's same the mess
we got into with security and decided not to repeat in the future.
> 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
