This topic describes the causes of and solutions for 503 errors in OSS.
DownloadTrafficRateLimitExceeded
Download traffic limit exceeded
Cause: The download bandwidth limit is exceeded.
Solution: See OSS bandwidth for the download bandwidth limits in each region. If your business requires a higher bandwidth limit, contact technical support.
UploadTrafficRateLimitExceeded
Upload traffic limit exceeded
Cause: The upload bandwidth limit is exceeded.
Solution: See OSS bandwidth for the upload bandwidth limits in each region. If your business requires a higher bandwidth limit, contact technical support.
MetaOperationQpsLimitExceeded
QPS limit for management APIs exceeded
Cause: The queries per second (QPS) limit for management APIs is exceeded.
OSS throttles the QPS of the following management APIs:
Service operations, such as GetService (ListBuckets)
Bucket operations, such as PutBucket and GetBucketLifecycle
CORS operations, such as PutBucketCORS and GetBucketCORS
LiveChannel operations, such as PutLiveChannel and DeleteLiveChannel
Solution: Retry the request after a few seconds.
ServiceUnavailable
Service temporarily busy
Cause: The OSS server is busy.
Solution: Retry the operation after a brief wait.
TotalQpsLimitExceeded
Total QPS limit exceeded
Cause: The number of queries per second (QPS) exceeds the limit.
Solution: The total QPS limit for a single account is 10,000. However, the achievable QPS varies based on the read/write method:
sequential read/write: 2,000
Using a sequential prefix (such as a timestamp or letters in alphabetical order) for many objects can concentrate their object indexes in a single bucket partition. This concentration degrades performance at a high request rate. We recommend that you avoid using a sequential prefix in object names when you upload a large number of objects. For more information about how to change a sequential prefix to a random prefix, see OSS performance best practices.
Non-sequential read/write: 10,000
If your business requires a higher QPS, contact technical support.
ActiveRequestLimitExceeded
Concurrent request limit exceeded
Cause: The number of concurrent requests exceeds the limit.
Solution: Contact technical support.
CpuLimitExceeded
Image Processing request rate exceeded
Cause: A high number of concurrent requests for Image Processing exceeded the CPU core limit.
Solution: Reduce the number of concurrent requests for Image Processing. If your business requires a higher limit, contact technical support.