-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kvserver: add minimum to cpu split threshold #98107
Copy link
Copy link
Closed
Labels
A-kv-distributionRelating to rebalancing and leasing.Relating to rebalancing and leasing.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)GA-blockerT-kvKV TeamKV Teambranch-release-23.1Used to mark GA and release blockers, technical advisories, and bugs for 23.1Used to mark GA and release blockers, technical advisories, and bugs for 23.1
Description
In #96128 we introduced CPU load based range splitting. to control when to split, kv.range_split.load_cpu_threshold was added.
Setting this value too low will result in excessive, destabilizing splitting, given some baseline foreground workload.
This issue is to add a minimum to this setting.
The current default is 500ms. A minimum of 50ms would be reasonable.
Jira issue: CRDB-25080
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-distributionRelating to rebalancing and leasing.Relating to rebalancing and leasing.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)GA-blockerT-kvKV TeamKV Teambranch-release-23.1Used to mark GA and release blockers, technical advisories, and bugs for 23.1Used to mark GA and release blockers, technical advisories, and bugs for 23.1