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: move dataBlockNum and parityBlockNum from BlockInfoStriped to INodeFile
Date Tue, 07 Apr 2015 05:28:12 GMT

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

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

bq. Otherwise we should use other ways to get these two information, maybe again through the
ECZone?

Yes. We should get this information when resolving the path. Therefore if we really need to
save memory in the future, we can even skip the two numbers in the INodeFile level maybe.

> Erasure coding: move dataBlockNum and parityBlockNum from BlockInfoStriped to INodeFile
> ---------------------------------------------------------------------------------------
>
>                 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