[
https://issues.apache.org/jira/browse/HDFS-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135425#comment-14135425
]
Zesheng Wu commented on HDFS-7044:
----------------------------------
bq. HDFS-6382 is standalone daemon outside NameNode, HDFS-7044 will be inside
NameNode, I believe HDFS-7044 will be more simple and efficient.
Yes, HDFS-6382 implements a standalone daemon, but it's not hard to start the
TtlManager inside NameNode, which is something like the trash emptier. What's
more important for HDFS-6382 is to supply the possibility for implementing a
general mechanism which can support various kinds of policies over the
namespace.
> Support retention policy based on access time and modify time, use XAttr to
> store policy
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-7044
> URL: https://issues.apache.org/jira/browse/HDFS-7044
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: namenode
> Reporter: zhaoyunjiong
> Assignee: zhaoyunjiong
> Attachments: Retention policy design.pdf
>
>
> The basic idea is set retention policy on directory based on access time and
> modify time and use XAttr to store policy.
> Files under directory which have retention policy will be delete if meet the
> retention rule.
> There are three rule:
> # access time
> #* If (accessTime + retentionTimeForAccess < now), the file will be delete
> # modify time
> #* If (modifyTime + retentionTimeForModify < now), the file will be delete
> # access time and modify time
> #* If (accessTime + retentionTimeForAccess < now && modifyTime +
> retentionTimeForModify < now ), the file will be delete
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
