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 Tue, 20 Jan 2015 06:43:36 GMT

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

Yi Liu commented on HDFS-7076:

Thanks Jing for updating the patch. Sorry for late review.

The patch itself is pretty good to me, I have few questions:
*1).* About the compatibility, original storage policies are pre-defined and hardcode, but
now we let admin to overwrite/remove, then how to handle the block storage policies for old
*2).* Even for new files, if admin changes the storage policies. Then user needs to utilize
the {{mover}} (the new data migration tool)?

My initial comments are as following, seems we need to rebase the patch again:
*1.* We should disallow the operations if the storage policy feature is not enabled.
*2.* Do we need to supply dfs admin command line for this feature?

> 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, 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

View raw message