Add config option to limit PostingsForMatchers() cache by size in bytes too #6151
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
In this PR I'm updating
mimir-prometheus
to get grafana/mimir-prometheus#533. It adds a config option to limit thePostingsForMatchers()
cache size by bytes too. I'm also deprecating the "limit by number of items", cause the plan is that the "limit by bytes size" will replace it. Even if these config options are experimental, I'm not directly removing the "limit by number of items" config option rightaway, to smooth the transition at Grafana Labs.I've manually tested it and looks working as expected 🤞
Which issue(s) this PR fixes or relates to
N/A
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]