[
https://issues.apache.org/jira/browse/HDFS-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165594#comment-16165594
]
Kai Zheng commented on HDFS-12414:
----------------------------------
TO CLARIFY: the commits here appear to be done by Sammi Chen, but actually it
did be me. It was caused by I shared a machine with Sammi. Sorry for the
confusion :(.
> 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
> Assignee: SammiChen
> Labels: hdfs-ec-3.0-nice-to-have
> Fix For: 3.0.0-beta1
>
> Attachments: HDFS-12414.001.patch, HDFS-12414.002.patch,
> HDFS-12414.003.patch, HDFS-12414.004.patch, HDFS-12414.005.patch,
> HDFS-12414.006.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
