hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7076) Persist Block Storage Policy in FSImage and Edit Log
Date Fri, 23 Jan 2015 06:39:35 GMT

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

Yi Liu commented on HDFS-7076:
------------------------------

Thanks Jing! 
Now I have some concern about whether we could have dynamic block storage Policy. For your
new proposal, that's better, actually I ever had the same thought about let the block storage
policies immutable. But I find another potential issue: the scalability, if we need to define
some new built-in block storage policies in future, how can we do? For example, we want to
add some new storage policies for HDFS EC, what policy name and policy id we should choose,
since user may already define some and there will be some conflicts.

I also want to ask [~szetszwo] for some suggestions or ideas?

> Persist Block Storage Policy in FSImage and Edit Log
> ----------------------------------------------------
>
>                 Key: HDFS-7076
>                 URL: https://issues.apache.org/jira/browse/HDFS-7076
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-7076.000.patch, HDFS-7076.001.patch, HDFS-7076.002.patch, HDFS-7076.003.patch,
HDFS-7076.004.patch, HDFS-7076.005.patch, HDFS-7076.005.patch, HDFS-7076.007.patch, editsStored
>
>
> Currently block storage policies are hard coded.  This JIRA is to persist the policies
in FSImage and Edit Log in order to support adding new policies or modifying existing policies.



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

Mime
View raw message