We currently throttle writes on the receiving store based on store health (e.g. via admission control or via specialized AddSSTable throttling). However, this only takes into account the local store health, and not the associated write cost on followers during replication, which isn't always throttled. We've seen this lead to hotspots where follower stores get overwhelmed, since the follower writes bypass admission control. A similar problem exists with snapshot application.
This has been touched on in several other issues as well:
Jira issue: CRDB-14642
Epic CRDB-15069
We currently throttle writes on the receiving store based on store health (e.g. via admission control or via specialized
AddSSTablethrottling). However, this only takes into account the local store health, and not the associated write cost on followers during replication, which isn't always throttled. We've seen this lead to hotspots where follower stores get overwhelmed, since the follower writes bypass admission control. A similar problem exists with snapshot application.This has been touched on in several other issues as well:
Jira issue: CRDB-14642
Epic CRDB-15069