You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
103142: c2c: introduce automatic distsql replanning r=stevendanna a=msbutler
This patch introduces the ability for a replication job to periodically refresh its physical plan. Here's how replanning works:
- The replication consumer's dist sql planner proposes a new physical plan every 10 minutes, as determined by the new `replication_stream.replan_flow.frequency` setting.
- it then computes how different the proposed plan is to the current plan. This patch computes difference as the number of _participating_ node changes (addition or removal) in the source and destination clusters as a fraction of the total number of participating nodes in both clusters in the previous plan.
- execute the new plan if this difference metric is greater than 0.1, the default of the new `repliaction_stream.replan_flow.threshold` setting.
In future work, we should consider replanning on data distribution changes, as outlined in cockroachdb#99164.
Fixescockroachdb#102900
Release note: None
Co-authored-by: Michael Butler <[email protected]>
0 commit comments