Skip to content

workload: use IMPORT parallelism proportional to available DistSQL pods in multi-tenant mode #78968

@nvb

Description

@nvb

In #78418, we addressed #75449 by using a parallelism of 1 when running IMPORT in multi-tenant mode. We set numNodes to 1 because we don't support DistSQL for IMPORTs in multi-tenant mode. Longer-term, however, we'll want an API which allows tenants to query the number of DistSQL pods available for these types of IMPORT jobs.

Jira issue: CRDB-14466

Epic CRDB-18499

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-multitenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-multitenantIssues owned by the multi-tenant virtual team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions