-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: use in-memory cache of tenant info in server controller #107827
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
Currently the code in server controller is using a periodic SQL poll loop to inspect the service mode of runnable tenants.
Since #106414 was merged, we now have a rangefeed-enabled cache of this state. So the SQL polling loop can be removed.
As a side benefit, this also makes it possible for the server controller to identify servers by tenant ID instead of by name.
Epic: CRDB-26691
Jira issue: CRDB-30208
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