hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7859) Erasure Coding: Persist erasure coding policies in NameNode
Date Fri, 15 Apr 2016 06:23:25 GMT

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

Rakesh R commented on HDFS-7859:
--------------------------------

bq. For the builtin schema and policies, IIRC, there was a consideration that we still need
to persist the schema and policy to indicate the software upgrades (so the builtin ones may
be changed).
Yes, changing built-in schema is an interesting case. If we end up in a case to change the
default one then persisting would be required. I think we can proceed to persist the ec policy
details in the fsimage and editlog. I'm just adding a thought to understand more - probably
we could explore whether layout version can be utilized to handle this kinda situations.

The patch need to rebase in latest code. Would you mind rebasing it, [~xinwei].

> Erasure Coding: Persist erasure coding policies in NameNode
> -----------------------------------------------------------
>
>                 Key: HDFS-7859
>                 URL: https://issues.apache.org/jira/browse/HDFS-7859
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Kai Zheng
>            Assignee: Xinwei Qin 
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-7859-HDFS-7285.002.patch, HDFS-7859-HDFS-7285.002.patch, HDFS-7859-HDFS-7285.003.patch,
HDFS-7859.001.patch, HDFS-7859.002.patch
>
>
> In meetup discussion with [~zhz] and [~jingzhao], it's suggested that we persist EC schemas
in NameNode centrally and reliably, so that EC zones can reference them by name efficiently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message