hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4884) [Umbrella] Block Placement Policy Optimizer
Date Thu, 06 Jun 2013 14:47:20 GMT

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

Junping Du updated HDFS-4884:
-----------------------------

    Issue Type: New Feature  (was: Bug)
    
> [Umbrella] Block Placement Policy Optimizer
> -------------------------------------------
>
>                 Key: HDFS-4884
>                 URL: https://issues.apache.org/jira/browse/HDFS-4884
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 1.2.0, 2.0.4-alpha
>            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

Mime
View raw message