-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Introduce cache flush rules [RHELDST-26144]
This change extends the cache flush config to support separate rules with different templates, enabled via patterns matched against candidate paths for flush. The goal here is to reduce the amount of unnecessarily flushed URLs/ARLs. In typical scenarios, we have three different CDN hosts in front of a single exodus-gw environment, with certain subtrees being only available from certain hosts. With the flat config structure existing before this change, we had no choice but to flush cache keys for all three of them for every path, even though each path is only relevant to one of the hosts. Hence, we were flushing 3x as many ARLs as we should be. With this change we can update the configuration to only flush cache for the necessary CDN host for each subtree, significantly cutting down the number of cache keys for flush. This commit is backwards-compatible with the old config style, so it can be safely deployed before updating exodus-gw.ini.
- Loading branch information
Showing
4 changed files
with
369 additions
and
73 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.