[jira] [Updated] (HDFS-5636) Enforce a max TTL per cache pool

["Andrew Wang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wang updated HDFS-5636:
------------------------------

    Attachment: hdfs-5636-1.patch

Good points Colin, that makes sense to me. Attached patch implements your proposed behavior. This involved splitting out an editlog variant of modifyDirective, since we want to keep it deterministic.

I use the somewhat weird constant of Long.MAX_VALUE/4 to indicate "never". Trying to do special handling with a -1 was error prone, and using Long.MAX_VALUE led to overflow bugs.

I also rolled up a few other fixes/cleanups:

* Fixed a bug in the duration conversion utility function
* Pretty-print CacheAdmin exceptions for pool operations
* Moved some constants into public classes

> 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
>         Attachments: hdfs-5636-1.patch
>
>
> 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)