Skip to content

Commit

Permalink
add suggested upper limit
Browse files Browse the repository at this point in the history
  • Loading branch information
taroface committed Jun 15, 2022
1 parent 2a8d00d commit 7550944
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion v22.1/cluster-setup-troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ W180817 17:01:56.510430 914 vendor/google.golang.org/grpc/clientconn.go:1293 grp

The `kv.snapshot_rebalance.max_rate` and `kv.snapshot_recovery.max_rate` [cluster settings](cluster-settings.html) set the rate limits at which [snapshots](architecture/replication-layer.html#snapshots) are sent to nodes. These settings can be temporarily increased to expedite replication during an outage or when scaling a cluster up or down.

However, if the settings are too high when nodes are added to the cluster, this can cause degraded performance and node crashes.
However, if the settings are too high when nodes are added to the cluster, this can cause degraded performance and node crashes. We recommend **not** increasing these values by more than 2 times their [default values](cluster-settings.html) without explicit approval from Cockroach Labs.

**Explanation:** If `kv.snapshot_rebalance.max_rate` and `kv.snapshot_recovery.max_rate` are set too high for the cluster during scaling, this can cause nodes to experience ingestions faster than compactions can keep up, and result in an [inverted LSM](architecture/storage-layer.html#inverted-lsms).

Expand Down

0 comments on commit 7550944

Please sign in to comment.