[
https://issues.apache.org/jira/browse/HDFS-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073551#comment-14073551
]
Daryn Sharp commented on HDFS-6526:
-----------------------------------
I see scalability and performance issues (maybe a few bugs) with the ttl
manager which make it unsuitable for large namesystems. I wasn't too concerned
because it's a "nice to have feature". I perked up when folding in the "must
have" trash emptier was mentioned in HDFS-6525.
Would you please elaborate on whether you plan to simply have the trash emptier
and ttl manager run as distinct services in the same adjunct process? Or do
you plan on the emptier actually leveraging/relying on ttls?
As a general comment, a feature like this is attractive but may be highly
dangerous. You many want to consider means to safeguard against a severely
skewed system clock, else the ttl manager might go on mass murder spree in the
filesystem...
> Implement HDFS TtlManager
> -------------------------
>
> Key: HDFS-6526
> URL: https://issues.apache.org/jira/browse/HDFS-6526
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client, namenode
> Affects Versions: 2.4.0
> Reporter: Zesheng Wu
> Assignee: Zesheng Wu
> Attachments: HDFS-6526.1.patch
>
>
> This issue is used to track development of HDFS TtlManager, for details see
> HDFS-6382.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
