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 "SammiChen (JIRA)" <ji...@apache.org> on 2017/09/11 03:14:00 UTC

[jira] [Created] (HDFS-12414) Ensure to use CLI command to enable/disable erasure coding policy

SammiChen created HDFS-12414:
--------------------------------

             Summary: Ensure to use CLI command to enable/disable erasure coding policy
                 Key: HDFS-12414
                 URL: https://issues.apache.org/jira/browse/HDFS-12414
             Project: Hadoop HDFS
          Issue Type: Improvement
            Reporter: SammiChen


Currently, there are two methods for user to enable/disable a erasure coding policy. One is through "dfs.namenode.ec.policies.enabled" property which is a static way to configure the enabled erasure coding policies. Another is through "enableErasureCodingPolicy" or "disabledErasureCodingPolicy" API which can enabled or disable erasure coding policy at runtime. 
When Namenode restart, there is potential state conflicts between the policy defined in "dfs.namenode.ec.policies.enabled" and policy saved in fsImage. To resolve the conflict and simplify the operation, it's better to use just one way and remove the old method configuring the property.



--
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