-
Notifications
You must be signed in to change notification settings - Fork 4k
Open
Labels
300-nodes-qualification-blockerA-disaster-recoveryC-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.O-testclusterIssues found or occurred on a test cluster, i.e. a long-running internal clusterIssues found or occurred on a test cluster, i.e. a long-running internal clusterP-2Issues/test failures with a fix SLA of 3 monthsIssues/test failures with a fix SLA of 3 monthsT-disaster-recoverybranch-masterFailures and bugs on the master branch.Failures and bugs on the master branch.
Description
Currently, we default the number of link workers to 32 by a cluster setting. But the number of workers should scale by the number of nodes, allowing online restore to better parallelize the link phase. In a recent large scale test with 300 nodes, for example, 90% of nodes were chilling.
Jira issue: CRDB-50608
Epic CRDB-48786
Metadata
Metadata
Assignees
Labels
300-nodes-qualification-blockerA-disaster-recoveryC-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.O-testclusterIssues found or occurred on a test cluster, i.e. a long-running internal clusterIssues found or occurred on a test cluster, i.e. a long-running internal clusterP-2Issues/test failures with a fix SLA of 3 monthsIssues/test failures with a fix SLA of 3 monthsT-disaster-recoverybranch-masterFailures and bugs on the master branch.Failures and bugs on the master branch.