[ https://issues.apache.org/jira/browse/TS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588523#comment-14588523 ]
ASF subversion and git services commented on TS-3580: ----------------------------------------------------- Commit 87bed9b390af30a6b6d4078adba885871e508a36 in trafficserver's branch refs/heads/master from [~psudaemon] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=87bed9b ] TS-3580: clang-format > 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)