kv,sql: improve rebalancing for incrementing indexes #81984
Labels
A-kv-distribution
Relating to rebalancing and leasing.
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-kv
KV Team
Projects
Is your feature request related to a problem? Please describe.
Heavy read/write workloads on incrementing indexes (timestamps are a common one) create moving hotspots in KV that are difficult to split+rebalance for better aggregate utilization. With such write patters, we're reading/writing to the right hand side of the last range in the index, and with our current structure of splitting off + rebalancing the RHS as a reaction to increased # of batch requests load, we'd be continuously rebalancing (with network costs/utilization) but still have single-range hostspots.
Describe the solution you'd like
A few ideas to improve here:
Additional context
Relevant internal issues: https://github.com/cockroachlabs/support/issues/1590, https://github.com/cockroachlabs/support/issues/1533.
Jira issue: CRDB-16157
The text was updated successfully, but these errors were encountered: