hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Deleted] (HDFS-10149) CLONE - Erasure coding: store EC schema and cell size in INodeFile and eliminate notion of EC zones
Date Tue, 15 Mar 2016 09:43:35 GMT

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

Vinayakumar B deleted HDFS-10149:
---------------------------------


> CLONE - Erasure coding: store EC schema and cell size in INodeFile and eliminate notion
of EC zones
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-10149
>                 URL: https://issues.apache.org/jira/browse/HDFS-10149
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: dragon
>            Assignee: Zhe Zhang
>
> We have [discussed | https://issues.apache.org/jira/browse/HDFS-7285?focusedCommentId=14357754&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14357754]
storing EC schema with files instead of EC zones and recently revisited the discussion under
HDFS-8059.
> As a recap, the _zone_ concept has severe limitations including renaming and nested configuration.
Those limitations are valid in encryption for security reasons and it doesn't make sense to
carry them over in EC.
> This JIRA aims to store EC schema and cell size on {{INodeFile}} level. For simplicity,
we should first implement it as an xattr and consider memory optimizations (such as moving
it to file header) as a follow-on. We should also disable changing EC policy on a non-empty
file / dir in the first phase.



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

Mime
View raw message