Skip to content

admission: make intent resolution subject to admission control #97108

@aliher1911

Description

@aliher1911

Is your feature request related to a problem? Please describe.
Creating enormous delete transaction could produce lots of intents. When transaction is committed, it could produce lots of intent cleanup and ranged intent cleanup requests. Currently those requests doesn't go through admission control and could overload L0 in pebble.

Jira issue: CRDB-24517

Epic CRDB-25458

Metadata

Metadata

Assignees

Labels

A-admission-controlA-kvAnything in KV that doesn't belong in a more specific category.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-sreFor issues SRE opened or otherwise cares about tracking.T-kvKV Team

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions