SammiChen created HDFS-12405:
--------------------------------
Summary: Complete remove "removed" state erasure coding policy
during Namenode restart
Key: HDFS-12405
URL: https://issues.apache.org/jira/browse/HDFS-12405
Project: Hadoop HDFS
Issue Type: Improvement
Components: erasure-coding
Reporter: SammiChen
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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
