This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
fix: log-cache memory consumption spike #355
Merged
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
The log-cache goes wild with memory consumption when it has more than 1 replica. This is a temporary fix.
mook-as
approved these changes
Jan 23, 2020
bikramnehra
pushed a commit
that referenced
this pull request
Apr 21, 2020
fix: log-cache memory consumption spike
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 log-cache goes wild with memory consumption when it has more than 1 replica. This is a temporary fix.
Motivation and Context
Please, see #241.
How Has This Been Tested?
Deployed in HA mode and made sure doppler only got 1 instance. Then ran smoke-tests (which has proven to cause this bug).
Types of changes
Checklist: