mimir: support for ingest-storage.ingestion-partition-tenant-shard-size #7804
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
This one updates the mimir operations, adding the support for the
-ingest-storage.ingestion-partition-tenant-shard-size
config, used with the "ingest storage" mode.As discussed privately with @pracucci, we would like to have a way to gradually apply the new configuration across internal Mimir deployments. Thus, the jsonnet only applies the flag if the
mimir._config.shuffle_sharding.ingest_storage_partitions_enabled
is raised.Also updated the calculated overrides, adding the support for
ingestion_partitions_tenant_shard_size
there.Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.