-
Notifications
You must be signed in to change notification settings - Fork 4.1k
schema: add a knob to control the speed of schema changes #36430
Copy link
Copy link
Closed
Labels
A-schema-changesC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-2Medium-high impact: many users impacted, risks of availability and difficult-to-fix data errorsMedium-high impact: many users impacted, risks of availability and difficult-to-fix data errorsT-disaster-recoveryX-staleno-issue-activity
Description
We should add a knob to allow for control of schema change speed in 19.1.
We should also use this knob to slow down schema changes in 19.1 to address issues like #34744, #36385, and others preemptively.
In 19.2, we can turn the knob back up after addressing CPU spike (#34744) and other stability concerns.
Without this knob, users can only turn off this implementation if they run into problems. Since we expect this implementation to be better than 2.1's overall, it would be a shame to need to direct users back to 2.1.
Epic CRDB-8816
Jira issue: CRDB-4499
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-schema-changesC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-2Medium-high impact: many users impacted, risks of availability and difficult-to-fix data errorsMedium-high impact: many users impacted, risks of availability and difficult-to-fix data errorsT-disaster-recoveryX-staleno-issue-activity