cockroachdb / cockroachdb/cockroach
restore: consider replanning more eagerly
Open
A-disaster-recovery
C-enhancement
O-24.3-scale-testing
O-testcluster
P-3
T-disaster-recovery
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
in the 150 node scale test, we do not replan as eagerly as we could, causing many nodes to hang out without any work. unsure if we should revisit this, given online restore.
Here's our current replanning heuristic in restore:
https://github.com/msbutler/cockroach/blob/master/pkg/ccl/backupccl/restore_job.go#L475
Jira issue: CRDB-44330
Contributor guide
Assessment
This issue has not been assessed yet.