Problem description
Your Alibaba Cloud account has exceeded its OSS queries per second (QPS) limit, causing requests to be throttled.
Causes
OSS enforces per-account QPS limits based on whether object names use sequential or non-sequential prefixes:
| Access pattern | QPS limit |
|---|---|
| Sequential read and write | 2,000 |
| Non-sequential read and write | 10,000 |
When the number of requests per second from your account exceeds the applicable limit, OSS throttles the excess requests.
Sequential object name prefixes (such as timestamps or alphabetical sequences) concentrate object indexes in a single partition. High request rates against that partition reduce throughput and make throttling more likely, even before the per-account ceiling of 10,000 QPS is reached.
Examples
None
Solutions
Reduce request frequency
Spread requests over time to stay within the QPS limit for your access pattern.
Switch to non-sequential object name prefixes
If object names use sequential prefixes, distribute the load by adding a short random hash at the start of each name:
| Sequential prefix (avoid) | Random prefix (recommended) |
|---|---|
logs/2024-01-01-app.log | a3f2/logs/2024-01-01-app.log |
2024010112-record.csv | 7b9c/2024010112-record.csv |
This distributes object indexes across multiple partitions. For implementation details, see OSS performance and scalability best practices.
Request a higher QPS limit
If your workload consistently requires more than 10,000 QPS, contact technical support to request an increase.