-
Notifications
You must be signed in to change notification settings - Fork 4.1k
jobs: destroy tenant keyspaces asynchronously #48775
Copy link
Copy link
Closed
Labels
A-jobsA-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)
Description
As part of #47904, we'll be introducing tenant destruction. It's tempting to make this is a synchronous operation that blows away all data in a tenant's keyspace immediately. This would probably work for the scale we're originally intending to support, but it's not a great solution in the long run.
We expect tenants to grow to arbitrarily large sizes, so we'll likely want to schedule tenant destruction as a long-running GC job in the system-tenants keyspace.
Reactions are currently unavailable
Metadata
Metadata
Labels
A-jobsA-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)