hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-6969) Archival Storage: INode#getStoragePolicyID should always return the latest storage policy
Date Fri, 29 Aug 2014 00:13:08 GMT
Jing Zhao created HDFS-6969:
-------------------------------

             Summary: Archival Storage: INode#getStoragePolicyID should always return the
latest storage policy
                 Key: HDFS-6969
                 URL: https://issues.apache.org/jira/browse/HDFS-6969
             Project: Hadoop HDFS
          Issue Type: Sub-task
            Reporter: Jing Zhao
            Assignee: Jing Zhao


In general, every file should only provide exact one storage policy for the Mover, no matter
its snapshot states. Suppose a file /foo/bar, and it is contained in snapshots s1 and s2 of
the root. If /foo/bar, /.snapshot/s1/foo/bar and /.snapshot/s2/foo/bar have different storage
policies, when running Mover, we have to select one of the storage policies, among which the
latest one should be the best. And if /foo/bar is deleted, we should still use its storage
policy before the deletion, since the file deletion should not trigger data migration.

Thus maybe what we can do is:
1. For a file with policy directly specified on it, alway follow the latest
2. Otherwise follow its latest parental path to identify its storage policy (simply following
the parent link)



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

Mime
View raw message