fix(cache): address in-memory cache invalidation using global tenant as key_prefix
#6976
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
This PR fixes an inconsistency in the redis
key_prefix
that was used when invalidating the cache entries which affected all the cache types (configs, accounts, routing, etc).The
delete_key
redis call during cache invalidation was usingglobal
as thekey_prefix
(key likeglobal:test_key
was being deleted in redis) while each of the tenants were reading using their correspondingkey_prefix
(key likepublic:test_key
was being set/read in redis).Additional Changes
Motivation and Context
How did you test it?
PUT/GET/UPDATE/DELETE on configs table as configs has cache usage
Checklist
cargo +nightly fmt --all
cargo clippy