6 ms·
I just destroyed my Backblaze buckets recently and realized they didn't have a "delete" button. You have to make a deletion API request for every single item in
by hombre_fatal 7y ago
I just destroyed my Backblaze buckets recently and realized they didn't have a "delete" button. You have to make a deletion API request for every single item in each bucket before you can delete a bucket.
I found that a bit ridiculous. My internet was so bad that I had to spin up an EC2 nano just to make a few billion requests and have them succeed. Took hours.
If backblaze wants to charge you on the way out (I wonder how much all those requests cost me), okay fine. But please just make a "delete bucket" button that does all this for us. If I was in a worse mood, I would've considered letting the account accrue balance until they did it for me.
- IfOnlyYouKnew 7y agoI seem to remember the same experience (not completely sure if it was Backblaze, though). Good to know I wasn't stupid. Couldn't shake the feeling at the time that I was missing something.
- jcims 7y agoAmazon S3 does the same thing. You can make bulk requests but you still are responsible for deleting all objects before removing the bucket. Agree it's stupid.
- _Propaganda_ 7y agoThis isn't strictly true - If you use the S3 dashboard the Delete Bucket button will abstract all the individual object deletes away for you.
- PopeDotNinja 7y agoHere's a video on deleting a bucket with a large number objects I just watched & found informative. It basically says something like you disable versioning, expire objects after 1 day, delete deletion markers, and delete deleted deletion markers (getting a little meta there). https://youtu.be/TPavkqp-Ymo https://youtu.be/TPavkqp-Ymo
- Karunamon 7y agoNo, you can nuke a bucket with stuff in it. I just realize I've never done this before, but the deletion screen calls out that all the contents will go away too. https://i.imgur.com/j1av6iE.png https://i.imgur.com/j1av6iE.png
- kalleboo 7y agoThat must be a somewhat recent addition - a year or two ago it wasn't possible (and the suggestion was what was posted in another comment - set the lifecycle rules to expire all the objects in a day) edit: actually the "don't close your browser window" warning leads me to believe that's just a client-side JavaScript solution which doesn't work with massive buckets (we had one with millions of objects)
- jandrese 7y agoWhy would the Javascript solution be inherently unable to deal with large buckets? Do we have to assume that they're taking some incredibly naive approach and trying to load every single ID into memory at once instead of streaming them out in chunks? It seems like Amazon should be capable of hiring an engineer who knows what they are doing.
- kalleboo 7y agoIt just seems like an inherently slow process. I remember at the time there was a python script someone wrote, which used the API to delete them in 1000 object chunks, and even running that with 10 threads the delete was going to take days and days.
- jcims 7y agoThe problem is the duration and durability of the exercise when you have millions of objects in the bucket. It could easily take days.
- jandrese 7y agoAt least it's the kind of problem you can come back to and restart if the process dies in the middle. You're bulk deleting data so maintaining integrity isn't a concern.
- nijave 7y agoYou can nuke a whole S3 bucket. There's a switch in the cli and a checkbox in the GUI. I think there's another option for deletion protection that disables that somewhere else
- jcims 7y agoI can't find the CLI option, the docs still say that the bucket must be empty[1]. There's something available in the management console but that doesn't really help with automated deployments and testing. [1] - https://docs.aws.amazon.com/cli/latest/reference/s3api/delete-bucket.html https://docs.aws.amazon.com/cli/latest/reference/s3api/delet... Edit: Found aws s3 rb --force, but this just automates the process of listing/deleting objects then deleting the bucket. When you have 7 million objects in a cloudtrail bucket, that can take days.
- Nyandalized 7y agoLooking at the pricing at: https://www.backblaze.com/b2/b2-transactions-price.html https://www.backblaze.com/b2/b2-transactions-price.html It seems that calling b2_delete_key is free. It's just not conveniently abstracted. Listing the items however if you don't already have a catalog is $4/M items
- jorams 7y ago> Listing the items however if you don't already have a catalog is $4/M items That doesn't seem correct. Each call to b2_list_keys can return up to 10 000 results, so it's $0.40/M items.
- deleted 7y ago[deleted]
- mrlinx 7y agoI was able to delete everything using their bucket browser UI. did you try that?
- hombre_fatal 7y agoThe web UI button specifically says the bucket cannot be deleted because it has contents.
- mr_t 7y agoThey did an AMA on Reddit a few months ago[0]. I remember this AMA in particular because they thoroughly explained why they designed some features in certain ways. Overall they said their target customers are the ones with absolutely no IT knowledge. I guess this part from one of their answers fits your complaint quite well: But here is the thing -> YOU can work around this problem, the naive customers CANNOT. Honestly, they are too computer-illiterate. But even computer illiterate people deserve to have their files backed up, and they are the target market for Backblaze Personal Backup. [1] From this point of view, I guess a "delete" button could be fatal for some of the older folks out there. But I don't use Backblaze, I don't know if my comparison makes sense and we both talk about the same thing. The Reddit quotes refers to their "Backblaze Personal Backup". [0] https://www.reddit.com/r/IAmA/comments/b6lbew/were_the_backblaze_cloud_team_managing_750/ https://www.reddit.com/r/IAmA/comments/b6lbew/were_the_backb... [1] https://www.reddit.com/r/IAmA/comments/b6lbew/were_the_backblaze_cloud_team_managing_750/ejlawg8/ https://www.reddit.com/r/IAmA/comments/b6lbew/were_the_backb...
- hombre_fatal 7y agoThere are all sorts of ways to created a delete-bucket button that avoids tech-illiterate fat fingering. Like simply burying it in options. Requiring end user to make a billion individual requests is almost as bad as making me call a number to delete my bucket. I’m voicing this here because I was surprised at the UX. I was happy with my backblaze experience otherwise. My bill was incredibly cheap for the amount of data and access I was using. I’d consider using it in the future for things we generally default to S3 for.
- typon 7y agoThere are good UI solutions to this problem... For example, a dialogue box that asks you to type "Yes I am sure I want to delete all my data, forever". We do things like this for internal tools at work, seems to go pretty well.
- wlesieutre 7y agoGitLab makes you do something similar to delete a repo, but not as explicit with the message. I think you just have to type the repository name in a box (to confirm you read the instructions) and click the delete button.
- Wouter33 7y agoYou can set a lifecycle rule for the bucket to delete all objects after a number of days. This way they wil be deleted automatically.