[
https://issues.apache.org/jira/browse/TS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586267#comment-14586267
]
ASF subversion and git services commented on TS-3580:
-----------------------------------------------------
Commit 7ff2d6189d0170b422b8d1bc3df1c2145198ee68 in trafficserver's branch
refs/heads/master from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=7ff2d61 ]
TS-3580: Use HttpCacheKey to enter the cache
Refactor the cache interface so that the HTTP cache lookup path
uses the new HttpCacheKey type, rather than fussing with URL objects
directly. This lets us use the per-request cache generation number
to access cache objects while the cache remains oblivious.
> 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)
