You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2013/06/01 05:53:22 UTC

[jira] [Reopened] (HDFS-3498) Make Replica Removal Policy pluggable and ReplicaPlacementPolicyDefault extensible for reusing code in subclass

     [ https://issues.apache.org/jira/browse/HDFS-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Junping Du reopened HDFS-3498:
------------------------------


Reopen jira for backport to branch-2
                
> Make Replica Removal Policy pluggable and ReplicaPlacementPolicyDefault extensible for reusing code in subclass
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3498
>                 URL: https://issues.apache.org/jira/browse/HDFS-3498
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 1.0.0, 2.0.0-alpha
>            Reporter: Junping Du
>            Assignee: Junping Du
>             Fix For: 3.0.0
>
>         Attachments: Hadoop-8471-BlockPlacementDefault-extensible.patch, HDFS-3498-branch-2.patch, HDFS-3498.patch, HDFS-3498-v2.patch, HDFS-3498-v3.patch, HDFS-3498-v4.patch, HDFS-3498-v5.patch
>
>
> ReplicaPlacementPolicy is already a pluggable component in Hadoop. However, the Replica Removal Policy is still nested in BlockManager that need to be separated out into a ReplicaPlacementPolicy then can be override later. Also it looks like hadoop unit test lack the testing on replica removal policy, so we add it here.
> On the other hand, as a implementation of ReplicaPlacementPolicy, ReplicaPlacementDefault still show lots of generic for other topology cases like: virtualization, and we want to make code in ReplicaPlacementPolicyDefault can be reused as much as possible so a few of its methods were changed from private to protected.

--
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