You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Huafeng Wang (JIRA)" <ji...@apache.org> on 2017/09/08 07:41:01 UTC
[jira] [Assigned] (HDFS-12405) Clean up removed erasure coding
policies from namenode
[ https://issues.apache.org/jira/browse/HDFS-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Huafeng Wang reassigned HDFS-12405:
-----------------------------------
Assignee: Huafeng Wang
> Clean up removed erasure coding policies from namenode
> ------------------------------------------------------
>
> Key: HDFS-12405
> URL: https://issues.apache.org/jira/browse/HDFS-12405
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: erasure-coding
> Reporter: SammiChen
> Assignee: Huafeng Wang
> Labels: hdfs-ec-3.0-nice-to-have
>
> Currently, when an erasure coding policy is removed, it's been transited to "removed" state. User cannot apply policy with "removed" state to file/directory anymore. The policy cannot be safely removed from the system unless we know there are no existing files or directories that use this "removed" policy. To find out whether there are files or directories which are using the policy is time consuming in runtime and might impact the Namenode performance. So a better choice is doing the work when NameNode restarts and loads Inodes. Collecting the information at that time will not introduce much extra overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org