You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2017/10/24 20:24:00 UTC

[jira] [Resolved] (HDFS-12686) Erasure coding system policy state is not correctly saved and loaded during real cluster restart

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

Xiao Chen resolved HDFS-12686.
------------------------------
    Resolution: Duplicate

Since HDFS-12682 should be able to handle this, and it's pretty hard to split that work into 2 jiras due to protobuf changes, I'll resolve this as a dup.

Thanks Sammi for filing the jira and Wei-Chiu for checking!

> Erasure coding system policy state is not correctly saved and loaded during real cluster restart
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-12686
>                 URL: https://issues.apache.org/jira/browse/HDFS-12686
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0-beta1
>            Reporter: SammiChen
>            Assignee: SammiChen
>            Priority: Blocker
>              Labels: hdfs-ec-3.0-must-do
>
> Inspired by HDFS-12682,  I found the system erasure coding policy state will  not  be correctly saved and loaded in a real cluster.  Through there are such kind of unit tests and all are passed with MiniCluster. It's because the MiniCluster keeps the same static system erasure coding policy object after the NN restart operation. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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