Allow cache_inactive_time on per site basis

Bug #1922927 reported by Benjamin Allot
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Content Cache Charm
Fix Released
High
Haw Loeung

Bug Description

The current cache_inactive_time setting is used for all locations/sites served by the charm.

We should be able to tweak it on a site basis.
I think a key "cache_inactive_time" under the site key itself would do, this latter overwriting the global one if set.

Related branches

Revision history for this message
Haw Loeung (hloeung) wrote :

https://code.launchpad.net/~hloeung/content-cache-charm/+git/content-cache-charm/+merge/414774 allows specifying extra configs such as "cache_inactive_time" per site/server. But I think we can do one better and use that to override cache_inactive_time for each of the proxy_cache_path.

Changed in content-cache-charm:
status: New → In Progress
assignee: nobody → Haw Loeung (hloeung)
importance: Undecided → High
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: In Progress → Fix Committed
Revision history for this message
Haw Loeung (hloeung) wrote :

Released as cs:~content-cache-charmers/content-cache-94

Changed in content-cache-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.