configure caches #108
Merged
configure caches #108
Conversation
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
wkloucek
force-pushed
the
configure-caches
branch
from
1a7cb87
to
ecf8773
Compare
rhafer
approved these changes
Nov 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The gateway and storage-users service normally share a common in-memory cache. Since they use active invalidation mechanisms we need to disable the cache or use an external cache as sonn as those two services don't run in the same process.
Related Issue
Motivation and Context
Fixes cache invalidation issues when running gateway and storage-users in different pods and enable the usage of external caches.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist:
make docs) and committed