After upgrading to the ac-2019 storage module three days ago, we’ve started receiving OSS storage quota exceeded alerts. Our upload operations are failing with “QuotaExceeded.Bucket” errors, even though we’re nowhere near our contracted storage limits.
Our setup:
- Standard OSS bucket with 10TB quota
- Current usage showing 6.2TB in console
- Lifecycle policies configured to delete objects older than 90 days
Error message:
Code: QuotaExceeded.Bucket
Message: Bucket storage quota exceeded
QuotaUsed: 10485760000000 bytes
The strange part is CloudMonitor shows only 6.2TB used, but the error claims we’ve hit the 10TB limit. Did the ac-2019 storage module change how storage quota is calculated? Our lifecycle policies should have been cleaning up old data automatically, but uploads are completely blocked now.
Ac-2019 changed how multipart uploads are counted against quota. Incomplete multipart uploads now count toward your storage quota, whereas before they didn’t. Check your bucket for abandoned multipart uploads - they might be consuming the missing 3.8TB.
We had the exact same issue after upgrading to ac-2019. The problem is that the console storage metrics don’t include incomplete multipart uploads in the displayed usage, but the quota enforcement does. It’s a UI bug that Alibaba is supposedly fixing. In the meantime, you have to query the actual quota usage via API to see the real numbers.
Also worth checking if your lifecycle policies are actually running. Ac-2019 changed the execution schedule from every 6 hours to once daily at midnight UTC. If your policies were set with relative timing expectations, they might not be executing as frequently as you think.