rangefeed: add scheduler priority shard for system ranges #110567
Labels
A-kv-rangefeed
Rangefeed infrastructure, server+client
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
O-premortem
Issues identified during premortem exercise.
To ensure system ranges don't get head-of-line blocked by user rangefeed traffic, we can add a separate priority shard in the scheduler for these, similarly to what we do in the Raft scheduler.
A couple of wrinkles: this will require a
sync.IntMap
lookup for every enqueue, which may have non-negligible cost, and we may not know whether a range is a system range when registering the rangefeed because span configs are themselves propagated via rangefeeds.Related to #110344.
Jira issue: CRDB-31508
Epic CRDB-26372
The text was updated successfully, but these errors were encountered: