You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2015/05/05 05:48:06 UTC

[jira] [Updated] (TS-3580) cache generation ID configuration

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

James Peach updated TS-3580:
----------------------------
    Fix Version/s: 6.0.0
         Assignee: James Peach

> cache generation ID configuration
> ---------------------------------
>
>                 Key: TS-3580
>                 URL: https://issues.apache.org/jira/browse/TS-3580
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Cache, Configuration
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 6.0.0
>
>
> It's common to want to purge the cache online, or to purge specific tenants in a multi-tenant cache. One reasonably straight forward implementation of this is to allow operators to specify a cache generation ID (a 64 bit integer that is hashed into the cache key). This is a global overridable configuration, so you can set it globally or for a specific remap rule.
> Note that it is a bit of a sharp tool, since if you lose or cannot propagate the correct generation ID you will take a cache miss.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)