-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
storcon: also support tenant deletion for safekeepers #11289
Conversation
7964 tests run: 7580 passed, 0 failed, 384 skipped (full report)Flaky tests (2)Postgres 17
Postgres 16
Code coverage* (full report)
* collected from Rust tests only The comment gets automatically updated with the latest test results
d72f1ec at 2025-03-19T16:09:39.238Z :recycle: |
3c3cbbf
to
937da2f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put some comments, but it would be more natural to finish https://neondb.slack.com/archives/C04KGFVUWUQ/p1742298363579099?thread_ts=1742297769.832709&cid=C04KGFVUWUQ
and
https://neondb.slack.com/archives/C04KGFVUWUQ/p1742287892184099
first.
Otherwise lgtm, it is in the right direction.
If a tenant gets deleted, delete also all of its timelines. We assume that by the time a tenant is being deleted, no new timelines are being created, so we don't need to worry about races with creation in this situation.
Unlike #11233, which was very simple because it listed the timelines and invoked timeline deletion, this PR obtains a list of safekeepers to invoke the tenant deletion on, and then invokes tenant deletion on each safekeeper that has one or multiple timelines.
Alternative to #11233
Builds on #11288
Part of #9011