Buckets invisible when I try to load them
Hi, my organization is running out of the free plan limit usage, and I wanted to try to delete a bucket to lower it as I'm in development mode and I don't need more from the platform. But unfortunately, the buckets don't seem to show up when I try to load them.
14 Replies
What do you mean by "try to load them"? Are they not in the UI?
You should use the Storage UI or Storage REST API to deleted buckets or files. Never delete from storage.buckets or storage.objects directly.
No, they're not showing in the UI. Therefor, the warning message in the dashboard say that my buckets are full. But none of them are showing up.
What is the warning saying? That you can't access storage anymore because you exceeded the limit?
"d.
Fair Use Policy applies and your service is restricted. Your projects are not able to serve requests and will respond with a 402 status code. You have exceeded your plan’s quota (Storage Size Exceeded). Upgrade your plan to lift restrictions or wait until your quota refills on your next billing period."
Yeah. Had one other user hit this recently. Must be some newer thing they are doing as there were no other hits I could find on it...
https://discord.com/channels/839993398554656828/1397531245948174357
Okay, so I must wait I guess...
I would still file a support request as it seems odd to not have a way out for size exceeded. I'm thinking it is not just hitting the limit, but ignoring it until you cross into a new billing period and they decide you are going to resolve it. Just a guess.
By billing period you mean the paid period ? Or just have I to wait until a new free plan to renew itself ?
Free plan still has a billing period where things reset every month. Just no cost.
I'm guessing if this crops up say a week before billing period ends and you don't fix it then it becomes a problem. At least you used to be able to reduce the size when you got the warning.
Ok, my free plan renew on the 7, just have to wait and coe back to you if it is necessary. If I don't recontact you this means that it worked as intended
Based on what you are saying it did crop up in this "billing" period and you could not fix it, which must be something new as until the other use posted have not seen it lock you out of storage to the point you could not clean up.
No it did not crop up in this billing period. It is older. But as I remember I already solved the problem by reducing the size of the file storage. But then I filled up the database with embedded vector and I didn't came back then to see if all was working. So might be the problem as well, isn't it ?
In fact I cannot remember if I have already deleted the problematic buckets...
Storage is files only. DB vectors themselves are stored in the .5GB database size metric.
Ok ok