[
https://issues.apache.org/jira/browse/TS-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3445:
------------------------------
Description:
Today, we have a way to clear the entire cache, e.g.
{code}
traffic_server -Cclear
{code}
It'd be useful to be able to do this with more finer granularity, e.g.
{code}
traffic_server -Cclear=1
{code}
or some such (I don't even know if the above would work with our clunky option
parsing ...). The use case would be that you setup some number of volumes, in
volume.config, and then use hosting.config to allocate certain volumes for
certain content.
For example, it's reasonable to have e.g.
volume.config:
{code}
volume=1 scheme=http size=50%
volume=2 scheme=http size=50%
{code}
hosting.config:
{code}
domain=ogre.com volume=1
domain=boot.org volume=2
{code}
Wish we had more APIs for this, but that's a separate Jira :).
was:
Today, we have a way to clear the entire cache, e.g.
{code}
traffic_server -Cclear
{code}
It'd be useful to be able to do this with more finer granularity, e.g.
{code}
traffic_server -Cclear=0,3
{code}
or some such (I don't even know if the above would work with our clunky option
parsing ...). The use case would be that you setup some number of volumes, in
volume.config, and then use hosting.config to allocate certain volumes for
certain content.
For example, it's reasonable to have e.g.
volume.config:
{code}
volume=1 scheme=http size=50%
volume=2 scheme=http size=50%
{code}
hosting.config:
{code}
domain=ogre.com volume=1
domain=boot.org volume=2
{code}
Wish we had more APIs for this, but that's a separate Jira :).
> Allow purging a specific volume
> -------------------------------
>
> Key: TS-3445
> URL: https://issues.apache.org/jira/browse/TS-3445
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Reporter: Leif Hedstrom
> Assignee: Alan M. Carroll
> Fix For: 6.0.0
>
>
> Today, we have a way to clear the entire cache, e.g.
> {code}
> traffic_server -Cclear
> {code}
> It'd be useful to be able to do this with more finer granularity, e.g.
> {code}
> traffic_server -Cclear=1
> {code}
> or some such (I don't even know if the above would work with our clunky
> option parsing ...). The use case would be that you setup some number of
> volumes, in volume.config, and then use hosting.config to allocate certain
> volumes for certain content.
> For example, it's reasonable to have e.g.
> volume.config:
> {code}
> volume=1 scheme=http size=50%
> volume=2 scheme=http size=50%
> {code}
> hosting.config:
> {code}
> domain=ogre.com volume=1
> domain=boot.org volume=2
> {code}
> Wish we had more APIs for this, but that's a separate Jira :).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
