[
https://issues.apache.org/jira/browse/HDFS-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848041#comment-13848041
]
Colin Patrick McCabe commented on HDFS-5636:
--------------------------------------------
OK, I misinterpreted the proposal here. I thought you wanted a single TTL
which would be applied to all directives in the pool. Instead, you want a max
(relative) TTL that can be set on anything added to the pool, at the time of
addition.
Are you proposing to silently add these TTLs when they're not present in the
request? Or hard error when we try to add something with a TTL that's "too
high"? The latter seems simpler.
> Enforce a max TTL per cache pool
> --------------------------------
>
> Key: HDFS-5636
> URL: https://issues.apache.org/jira/browse/HDFS-5636
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: caching, namenode
> Affects Versions: 3.0.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
>
> It'd be nice for administrators to be able to specify a maximum TTL for
> directives in a cache pool. This forces all directives to eventually age out.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
