hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Sasaki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8494) Remove hard-coded chunk size in favor of ECZone
Date Tue, 09 Jun 2015 04:22:00 GMT

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

Kai Sasaki commented on HDFS-8494:

Thanks all for sharing inspiring ideas and thoughts! I think removing hard-coded chunk-size
requires more discussion and seems to have some dependencies to solve. 
So in this stage, we can assume chunk sizes used in EC cluster are the same to {{HdfsConstants}}

I think the basic idea is that we'd better decouple the logic of the blocks, which belong
to the storage level, from the files.

I agree with [~jingzhao]. In order to remove hard-coded value, it might be necessary to discuss
more about the self-explained data structure in all cases. 

Can we move this JIRA to under HDFS-8030 or HDFS-8031? 

> Remove hard-coded chunk size in favor of ECZone
> -----------------------------------------------
>                 Key: HDFS-8494
>                 URL: https://issues.apache.org/jira/browse/HDFS-8494
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: HDFS-7285
>            Reporter: Kai Sasaki
>            Assignee: Kai Sasaki
>             Fix For: HDFS-7285
>         Attachments: HDFS-8494-HDFS-7285-01.patch, HDFS-8494-HDFS-7285-02.patch
> It is necessary to remove hard-coded values inside NameNode configured in {{HdfsConstants}}.
In this JIRA, we can remove {{chunkSize}} gracefully in favor of HDFS-8375.
> Because {{cellSize}} is now originally stored only in {{ErasureCodingZone}}, {{BlockInfoStriped}}
can receive {{cellSize}} in addition to {{ECSchema}} when its initialization.

This message was sent by Atlassian JIRA

View raw message