-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kvserver: store with high read amplification should not be a target of rebalancing #73714
Copy link
Copy link
Labels
A-kv-replication-constraintsC-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)T-kvKV TeamKV Team
Description
Looking at a 6 hour interval of a node with a single store that had consistently high read amplification of > 1600, there are 3055 log entries containing "applying snapshot of type INITIAL".
The allocator should not add replicas to a store that is unhealthy in this manner.
There are also 11804 "removing replica" log statements, so probably the allocator has some signal it is using to shed load.
(the Cockroach Labs internal link for these logs https://upload.cockroachlabs.com/receive/?thread=J0LX-VAFS&packageCode=3V8ZJ2nVEB0zprhPefmADBbjcHJ1YEnIerx9xAyeqdE#keyCode=q1HsA9iW08Ftw0eGrEXYMckv635vIQbmw8s-Y5i3FxI)
cc: @aayushshah15
Jira issue: CRDB-11703
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-replication-constraintsC-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)T-kvKV TeamKV Team