[
https://issues.apache.org/jira/browse/TS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586268#comment-14586268
]
ASF subversion and git services commented on TS-3580:
-----------------------------------------------------
Commit 9f71421a15e1a8ee51fd00782947535764a60672 in trafficserver's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=9f71421 ]
TS-3580; Apply the cache generation number in ICP
In the ICP support, use the current cache generation number to
access cache objects. Note that at this point we cannot tell whether
the cache generation has been overridden for a specific object; we
can only use the global configuration.
> 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)
