[
https://issues.apache.org/jira/browse/HDFS-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Zheng updated HDFS-12405:
-----------------------------
Description: 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. (was: 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 is no existing files or directories use this
"remove" policy. To find out whether there is files or directories which are
using the policy is time consuming in runtime and might impact the Namenode
performance. So a better choice is do the work when NameNode restarts and loads
Inode one by one. Collect the information at that time will not introduce much
extra workloads. )
Summary: Clean up removed erasure coding policies from namenode (was:
Complete remove "removed" state erasure coding policy during Namenode restart)
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
