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/06 16:47:20 UTC

[jira] [Created] (HDFS-4884) [Umbrella] Block Placement Policy Optimizer

Junping Du created HDFS-4884:
--------------------------------

             Summary: [Umbrella] Block Placement Policy Optimizer
                 Key: HDFS-4884
                 URL: https://issues.apache.org/jira/browse/HDFS-4884
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.0.4-alpha, 1.2.0
            Reporter: Junping Du
            Assignee: Junping Du


The BlockPlacementPolicy (BPP) is extensible and already multiple instances in system: BlockPlacementPolicyDefault, BlockPlacementPolicyWithNodeGroup, BlockPlacementPolicyRAID, etc. When cluster is switched from one BPP to another BPP, HDFS will not check if block locations conform the new BPP. Now, you can manually fsck on specific directory to identify replica placement policy is violated for some blocks but have no way to fix it so far. We should provide way to fix it. Also, in the long term, we should allow multiple BPPs co-existing on the same HDFS cluster for different purpose of data, i.e. we should allow some old, infrequently accessed data/directory to under RAID policy so that can save space. 

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