hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8059) Erasure coding: revisit how to store EC schema and cellSize in NameNode
Date Mon, 20 Jul 2015 22:42:05 GMT

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

Jing Zhao commented on HDFS-8059:
---------------------------------

bq. Breaking rename as I stated above is a huge limitation.

Could you please provide more details about how putting EC schema in INodeFile can solve the
rename problem (assuming the rename is across two EC zones with different EC schema)? Please
note with wrong schemas an EC file cannot be correctly read.

bq. This JIRA is also on the shortlist of remaining issues for the EC branch

Can you direct me to this list?

> Erasure coding: revisit how to store EC schema and cellSize in NameNode
> -----------------------------------------------------------------------
>
>                 Key: HDFS-8059
>                 URL: https://issues.apache.org/jira/browse/HDFS-8059
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: HDFS-7285
>            Reporter: Yi Liu
>            Assignee: Yi Liu
>         Attachments: HDFS-8059.001.patch
>
>
> Move {{dataBlockNum}} and {{parityBlockNum}} from BlockInfoStriped to INodeFile, and
store them in {{FileWithStripedBlocksFeature}}.
> Ideally these two nums are the same for all striped blocks in a file, and store them
in BlockInfoStriped will waste NN memory.



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

Mime
View raw message