Clean up an old blob store once its change is resolved #342

Closed
opened 2026-11-09 18:12:13 +00:00 by jcoffey-dev · 2 comments
Owner

Follow-up to #333.

Once a blob store change is resolved (the copy ended copied), every blob the server holds is in the new store, but nothing is ever deleted from the old one (BM-7). That stays the administrator's job, and for a bucket or a directory it can mean a lot of space.

An explicit action for this would help: delete from the old store only blobs that are in the new one and verified there. It's only allowed after the change is resolved, and it's audited. The old store's settings are dropped on resolution today, so they'd need to be kept until the cleanup runs or the change is dismissed. Snapshot and backup interplay need thought before this is specced.

Follow-up to #333. Once a blob store change is resolved (the copy ended `copied`), every blob the server holds is in the new store, but nothing is ever deleted from the old one (BM-7). That stays the administrator's job, and for a bucket or a directory it can mean a lot of space. An explicit action for this would help: delete from the old store only blobs that are in the new one and verified there. It's only allowed after the change is resolved, and it's audited. The old store's settings are dropped on resolution today, so they'd need to be kept until the cleanup runs or the change is dismissed. Snapshot and backup interplay need thought before this is specced.
jcoffey-dev added the
priority
p3
enhancement
labels 2026-11-09 18:12:13 +00:00
jcoffey-dev self-assigned this 2026-11-09 20:53:13 +00:00
Author
Owner

Done in #358 (spec in #357). A resolved change keeps its old store, and action cleanUp deletes from it only what the current store has and checks out; the rest is kept and reported. Preview first with dryRun; a real run needs confirm set to the change id. Ships in the next server rc; console, CLI and docs to follow.

Done in #358 (spec in #357). A resolved change keeps its old store, and action cleanUp deletes from it only what the current store has and checks out; the rest is kept and reported. Preview first with dryRun; a real run needs confirm set to the change id. Ships in the next server rc; console, CLI and docs to follow.
Author
Owner

The console, CLI and docs for the cleanup are merged too: inbuxa-admin #185 ("Clean up the old store" with a preview, gated on older backups), inbuxa-cli #7 (store clean-up / store stop-clean-up), and inbuxa.org #146 ("Cleaning up the old store", published with the release). #359 fixes the wording of a different blob of the same size. They ship in server 27.1-rc.19 and Admin 27.1-rc.12.

The console, CLI and docs for the cleanup are merged too: inbuxa-admin #185 ("Clean up the old store" with a preview, gated on older backups), inbuxa-cli #7 (`store clean-up` / `store stop-clean-up`), and inbuxa.org #146 ("Cleaning up the old store", published with the release). #359 fixes the wording of a `different` blob of the same size. They ship in server 27.1-rc.19 and Admin 27.1-rc.12.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#342