cockroachdb / cockroachdb/cockroach
crosscluster/logical: automatically replan on lagging source node
Open
A-disaster-recovery
C-enhancement
P-2
T-disaster-recovery
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
We have observed in large scale LDR deployments that one src-dest ldr proc pair is holding the replicated time back, and the proc on the source is conducting a ton of catchup scans. Let's copy over the auto replanning logic we have in PCR for this into LDR, allowing the source side to distribute that catchup scan work.
Jira issue: CRDB-42018
Contributor guide
Assessment
This issue has not been assessed yet.