CockroachDB Range Rebalancing Language Collocations
Practise the standard verbs for managing CockroachDB range rebalancing.
0 / 5 completed
1 / 5
Fill in: 'We ___ a manual range rebalance after adding a node so new capacity actually absorbs load, rather than sitting empty while old nodes stay overloaded.'
We 'trigger a rebalance' — the standard, established collocation for manually initiating range redistribution across nodes. The other options aren't the recognised term here.
2 / 5
Fill in: 'Waiting for automatic rebalancing alone after a large data import can ___ the newest nodes under-utilised for hours while older ones stay saturated.'
We say relying on automation will 'leave' new nodes under-utilised — the standard, natural collocation for the resulting imbalance. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ range distribution across nodes continuously, since an uneven split can silently concentrate hot ranges on a single node long before anyone notices the imbalance.'
We 'monitor' distribution — the standard collocation for ongoing observation of how data is spread across a cluster. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ range replica placement against the configured zone constraints after a rebalance, so a critical range doesn't end up entirely within one failure domain.'
We 'verify' placement — the standard, simple collocation for confirming replicas landed where zone rules require. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ rebalancing bandwidth during business hours so a large redistribution doesn't compete with live query traffic for the same disk and network capacity.'
We 'throttle bandwidth' — the standard, established collocation for capping a background process's resource usage. The other options aren't the recognised term here.