hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6847) Archival Storage: Support storage policy on directories
Date Fri, 15 Aug 2014 05:06:19 GMT

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

Tsz Wo Nicholas Sze commented on HDFS-6847:
-------------------------------------------

We should add setStoragePolicyID methods to INode.  Then, move FSDirectory.setDirStoragePolicy
to INodeDirectory.  Further FSDirectory.unprotectedSetStoragePolicy(..) should just call setStoragePolicyID
and does not need to check whether the INode is a file or a directory.


> Archival Storage: Support storage policy on directories
> -------------------------------------------------------
>
>                 Key: HDFS-6847
>                 URL: https://issues.apache.org/jira/browse/HDFS-6847
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: balancer, namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-6847.000.patch, HDFS-6847.001.patch
>
>
> This jira plans to add storage policy support on directory, i.e., users can set/get storage
policy for not only files but also directories.
> We allow users to set storage policies for nested directories/files. For a specific file/directory,
its storage policy then should be its own storage policy, if it is specified, or the storage
policy specified on its nearest ancestral directory. E.g., for a path /foo/bar/baz, if two
different policies are set on foo and bar (p1 for foo and p2 for bar), the storage policies
for baz, bar, and foo should be p2, p2, and p1, respectively.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message