Skip to content

ref(allocation-policies): Add key_by to ConcurrentRateLimitAllocationPolicy - #8634

Closed
dezzeddi wants to merge 1 commit into
masterfrom
dani/crl-concurrent-limit-key-by
Closed

dezzeddi wants to merge 1 commit into
masterfrom
dani/crl-concurrent-limit-key-by

Conversation

@dezzeddi

Copy link
Copy Markdown
Member

ConcurrentRateLimitAllocationPolicy has concurrent_limit plus four level-named param overrides (referrer_project_override, referrer_organization_override, project_override, organization_override). The lowest matching override wins and moves the count to another Redis bucket.

  • Removed the four overrides. No config sets them today; per-tenant limits are already match blocks with concurrent_limit.
  • Added key_by: tenant (default, today's bucket), organization or organization_referrer. The org buckets use the same names the removed overrides used.
  • explanation no longer has an overrides field.
  • Schema: key_by allowed as a string on policies.

No behaviour change with current config. Also applies to DeleteConcurrentRateLimitAllocationPolicy (subclass).

…Policy

Replace the four *_override param configs with key_by, which picks the tenant
the concurrency count is kept for: tenant (default, today's bucket),
organization or organization_referrer. Per-tenant limits go in match blocks
as concurrent_limit. No override is set in any region today.
@dezzeddi

Copy link
Copy Markdown
Member Author

Combined into #8643.

@dezzeddi dezzeddi closed this Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant