This repository was archived by the owner on Apr 28, 2025. It is now read-only.
Increase default store-gateway memory request and limit #322
Conversation
This file contains hidden or 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
Signed-off-by: Marco Pracucci <[email protected]>
Signed-off-by: Marco Pracucci <[email protected]>
pstibrany
approved these changes
Jun 8, 2021
simonswine
pushed a commit
to grafana/mimir
that referenced
this pull request
Dec 20, 2021
…tore-gateway-mem Increase default store-gateway memory request and limit
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
What this PR does:
When we initially introduced the Cortex blocks storage support to the mixin, we put some "random" values for new services resources request/limit due to a lack of production knowledge. We learned store-gateway memory was definitely underprovisioned and we typically run it with way more memory. In this PR I'm proposing to increase it in the OSS mixin too.
Which issue(s) this PR fixes:
N/A
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]