-
Notifications
You must be signed in to change notification settings - Fork 4.1k
multitenant: Randomly test over all three tenancy configurations #111134
Copy link
Copy link
Closed
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)GA-blockerO-premortemIssues identified during premortem exercise.Issues identified during premortem exercise.T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual teambranch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2
Description
We currently have three supported tenancy configurations in which to run CRDB:
- Single tenant
- Shared-process multi-tenant (aka cluster virtualization)
- Separate-process multi-tenant
#76582 (and several follow-on PRs) allowed for the ability to randomly test the first two configurations. This issue should add the third configuration to the randomization.
Epic CRDB-31933
Jira issue: CRDB-31784
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-multitenancyRelated to multi-tenancyRelated to multi-tenancyC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)GA-blockerO-premortemIssues identified during premortem exercise.Issues identified during premortem exercise.T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual teambranch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2