Skip to content

[DQE-1] Metric Name Shard Size#7686

Closed
eeldaly wants to merge 1 commit into
cortexproject:masterfrom
eeldaly:dqe-split/1-metric-name-shard-limit
Closed

[DQE-1] Metric Name Shard Size#7686
eeldaly wants to merge 1 commit into
cortexproject:masterfrom
eeldaly:dqe-split/1-metric-name-shard-limit

Conversation

@eeldaly

@eeldaly eeldaly commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

This PR is part 1 of 8 to get the changes made here by Ruby (https://github.com/rubywtl/cortex/commits?author=rubywtl) upstreamed and working for the distributed query engine path.


Introduce the metric_name_shard_size per-tenant limit and the GetMetricNameShardSize accessor on the tripperware Limits interface, implemented by validation.Overrides. Update the interface mocks and the overrides exporter test fixture accordingly.

This is the configuration foundation for distributed query execution (DQE) metric-name sharding.

What this PR does:

Which issue(s) this PR fixes:
Fixes #

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]
  • docs/configuration/v1-guarantees.md updated if this PR introduces experimental flags

Introduce the metric_name_shard_size per-tenant limit and the
GetMetricNameShardSize accessor on the tripperware Limits interface,
implemented by validation.Overrides. Update the interface mocks and the
overrides exporter test fixture accordingly.

This is the configuration foundation for distributed query execution
(DQE) metric-name sharding.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant