hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11633) FSImage failover disables all erasure coding policies
Date Fri, 07 Apr 2017 22:48:41 GMT

     [ https://issues.apache.org/jira/browse/HDFS-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Wang updated HDFS-11633:
       Resolution: Fixed
    Fix Version/s: 3.0.0-alpha3
           Status: Resolved  (was: Patch Available)

Nice find and fix [~jojochuang], committed to trunk!

> FSImage failover disables all erasure coding policies 
> ------------------------------------------------------
>                 Key: HDFS-11633
>                 URL: https://issues.apache.org/jira/browse/HDFS-11633
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: erasure-coding, namenode
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Critical
>              Labels: hdfs-ec-3.0-must-do
>             Fix For: 3.0.0-alpha3
>         Attachments: HDFS-11633.001.patch, HDFS-11633.002.patch, HDFS-11633.test.patch
> If NameNode fails to load the fsimage in the first NameNode metadata directory, it accidentally
clears all enabled erasure coding policies in ErasureCodingPolicyManager.
> Even if the NameNode configures multiple fsimage metadata directory and it successfully
loads the second one, enabled erasure coding policies are not restored.
> In the current implementation, we do not have a ErasureCodingPolicyManager section in
fsimage, so a fsimage reload does not reload ECPM.
> The easiest fix before ECPM section is implemented, is don't clear ECPM when FSNamesystem
is cleared.

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