Add in uniqueness to cache keys to mitigate clashes on multisite inst… #14485
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.
…alls
Overview
in our system we have been seeing some issues where the unique key already exists in the cache database when it goes to try and insert. This aims to try and fix it by adding some uniquness in this case the domain_id to the cache key
Before
CacheKeys could be the same across different domains
After
Cache Keys unique to the specific domain
ping @totten @eileenmcnaughton thoughts?