Skip to content

kv,server: enable some degree of range descriptor pre-fetching in secondary tenants #91433

@ajwerner

Description

@ajwerner

Is your feature request related to a problem? Please describe.
Currently we do not pre-fetch any additional range descriptors. See

// Until we add protection in the Internal service implementation to
// prevent prefetching from traversing into RangeDescriptors owned by
// other tenants, we must disable prefetching.
PrefetchNum: 0,

Describe the solution you'd like
We should add some logic to filter range descriptors returned based on the tenant and then use the same pre-fetching logic we use in regular KV.

Epic: CRDB-18596

Jira issue: CRDB-21259

Metadata

Metadata

Assignees

Labels

C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions