hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SammiChen (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-12414) Ensure to use CLI command to enable/disable erasure coding policy
Date Wed, 13 Sep 2017 09:04:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164351#comment-16164351

SammiChen edited comment on HDFS-12414 at 9/13/17 9:03 AM:

Thanks Huafeng and Kai for helping review the patch! 

Rebase the patch

was (Author: sammi):
rebase the patch

> 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
>         Attachments: HDFS-12414.001.patch, HDFS-12414.002.patch, HDFS-12414.003.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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message