You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2016/03/15 10:43:35 UTC

[jira] [Deleted] (HDFS-10125) CLONE - Erasure coding: Persist cellSize in BlockInfoStriped and StripedBlocksFeature

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

Vinayakumar B deleted HDFS-10125:
---------------------------------


> CLONE - Erasure coding: Persist cellSize in BlockInfoStriped and StripedBlocksFeature
> -------------------------------------------------------------------------------------
>
>                 Key: HDFS-10125
>                 URL: https://issues.apache.org/jira/browse/HDFS-10125
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: dragon
>            Assignee: Walter Su
>
> Zhe Zhang, Kai Zheng and I had a offline discussion. Here is what we thought:  Add a cellSize field in BlockInfoStriped as a workaround, and deal with memory usage in follow-on.(HDFS-8059)
> discussion in HDFS-8494:
> from Walter Su:
> {quote}
> I think BlockInfoStriped needs to keep cellSize.
> {quote}
> from [~vinayrpet]:
> {quote}
> I too was thinking the same when the FSImageLoader problem has came up. This will increase the memory usage by ~4bytes for each block though.
> {quote}
> from [~jingzhao]
> {quote}
> -Also, we should consider adding a chunk size field to StripedBlockProto and removing the cell size field from HdfsFileStatus. In this way we can access the chunk size information in the storage layer.-
> {quote}
> ==
> update:
> from [~jingzhao]
> {quote}
> For fsimage part, since HDFS-8585 just removes StripedBlockProto, I guess what we can do here is to either 1) add the cellSize information into StripedBlocksFeature in fsimage.proto, or 2) bring StripedBlockProto back and put block info and cell size there.
> {quote}



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