-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kvserver: selectively enqueue replicas into the replicate queue on span config updates #108795
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
Comments
kvoli
added
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
A-kv-distribution
Relating to rebalancing and leasing.
labels
Aug 15, 2023
kvoli
added a commit
to kvoli/cockroach
that referenced
this issue
Aug 15, 2023
`kv.enqueue_in_replicate_queue_on_span_config_update.enabled` controls whether replicas are enqueued into the replicate queue, upon a span config update. The setting was disabled due to overhead. Re-enable the setting, as we anticipate significantly reducing the overhead in Informs: cockroachdb#108795 Release note (ops change): Enable `kv.enqueue_in_replicate_queue_on_span_config_update.enabled` by default. This setting speeds up how quickly replication changes begin, after changing a related configuration e.g. database primary region or replication factor.
andrewbaptist
added a commit
to andrewbaptist/cockroach
that referenced
this issue
Aug 16, 2023
Previously we would queue replicas for split, merge and replicate changes on every change to the span configs including PTS changes. This was inefficient and now we check if the change to the SpanConfig is significant. Informs: cockroachdb#107977 Fixes: cockroachdb#108795 Epic: none Release note: None
andrewbaptist
added a commit
to andrewbaptist/cockroach
that referenced
this issue
Sep 8, 2023
Previously we would queue replicas for split, merge and replicate changes on every change to the span configs including PTS changes. This was inefficient and now we check if the change to the SpanConfig is significant. Informs: cockroachdb#107977 Fixes: cockroachdb#108795 Epic: none Release note: None
andrewbaptist
added a commit
to andrewbaptist/cockroach
that referenced
this issue
Sep 8, 2023
Previously we would queue replicas for split, merge and replicate changes on every change to the span configs including PTS changes. This was inefficient and now we check if the change to the SpanConfig is significant. Informs: cockroachdb#107977 Fixes: cockroachdb#108795 Epic: none Release note: None
craig bot
pushed a commit
that referenced
this issue
Sep 13, 2023
108809: kvserver: queue replicas on significant span config changes r=kvoli a=andrewbaptist Previously we would queue replicas for split, merge and replicate changes on every change to the span configs including PTS changes. This was inefficient and now we check if the change to the SpanConfig is significant. Informs: #107977 Fixes: #108795 Epic: none Release note: None Co-authored-by: Andrew Baptist <[email protected]>
This was referenced Jul 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Is your feature request related to a problem? Please describe.
In #100349, we began enqueuing replicas (into the replicate queue) upon receiving span config updates. This came with an unreasonable overhead in clusters with many ranges, described in #108724.
Not all span config updates require replication changes. Only changes to
lease_preferences
,constraints
,voter_constraints
,num_replicas
andnum_voters
could possibly require replication changes.Describe the solution you'd like
Only enqueue into the replicate queue for span config updates when there's a change to one of the fields mentioned above, from the last span config seen.
Jira issue: CRDB-30641
The text was updated successfully, but these errors were encountered: