hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nawab Qureshi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4884) Provide a way to enforce new Block Placement Policy on existing data after switching from old one
Date Thu, 21 Jan 2016 09:04:39 GMT

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

Nawab Qureshi updated HDFS-4884:
--------------------------------
    Target Version/s: 2.7.1  (was: 3.0.0)

> Provide a way to enforce new Block Placement Policy on existing data after switching
from old one
> -------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4884
>                 URL: https://issues.apache.org/jira/browse/HDFS-4884
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message