hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5636) Enforce a max TTL per cache pool
Date Fri, 20 Dec 2013 23:28:10 GMT

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

Colin Patrick McCabe updated HDFS-5636:
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 3.0.0
    Target Version/s: 3.0.0
              Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 3.0.0
>
>         Attachments: hdfs-5636-1.patch, hdfs-5636-2.patch, hdfs-5636-3.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)

Mime
View raw message