-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: blocked mixed-style deployments [CRDB-14537 followup] #93145
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)T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual team
Description
Requested by @andreimatei and @dhartunian
For the time being, we are going to work under the assumption that for a given tenant, either
- all SQL servers are in-process with KV,
- OR all SQL servers are out-of-process.
but not both.
As of v23.1, our main plan to enforce this assumption is via runbooks (i.e. tell users "don't do that").
However, we probably want a check in the product to prevent mistakes.
This could be done e.g. by looking at the sql instances/sessions table to see whether there's a session open.
Jira issue: CRDB-22187
Epic CRDB-26691
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)T-multitenantIssues owned by the multi-tenant virtual teamIssues owned by the multi-tenant virtual team