hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7866) Erasure coding: NameNode manages multiple erasure coding policies
Date Wed, 09 Mar 2016 00:50:41 GMT

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

Zhe Zhang commented on HDFS-7866:

bq. ErasureCodingPolicyProto is only used in getFileStatus RPC
[~jingzhao] Seems {{getErasureCodingPolicy}} and {{getErasureCodingPolicies}} are also using
the proto? Could you also elaborate a bit why this means the new filed only breaks compatibility
during upgrades?

IIUC, the incompatibility comes from a newer client (a jar after this commit) accessing an
older NN (a jar before this commit), right?

> Erasure coding: NameNode manages multiple erasure coding policies
> -----------------------------------------------------------------
>                 Key: HDFS-7866
>                 URL: https://issues.apache.org/jira/browse/HDFS-7866
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Kai Zheng
>            Assignee: Rui Li
>         Attachments: HDFS-7866-v1.patch, HDFS-7866-v2.patch, HDFS-7866-v3.patch, HDFS-7866.10.patch,
HDFS-7866.11.patch, HDFS-7866.12.patch, HDFS-7866.13.patch, HDFS-7866.4.patch, HDFS-7866.5.patch,
HDFS-7866.6.patch, HDFS-7866.7.patch, HDFS-7866.8.patch, HDFS-7866.9.patch
> This is to extend NameNode to load, list and sync predefine EC schemas in authorized
and controlled approach. The provided facilities will be used to implement DFSAdmin commands
so admin can list available EC schemas, then could choose some of them for target EC zones.

This message was sent by Atlassian JIRA

View raw message