Azure Page blob : Throttling observed due to IO limit reached
- Views:
- 515
- Visibility:
- Public
- Votes:
- 0
- Category:
- cloud-volumes-ontap-cvo
- Specialty:
- microsoft_azure
- Last Updated:
Applies to
- CVO
- AZURE
Issue
Throttling observed on storage account :Fri Aug 25 21:18:25 0000 [XXXXXXXXXXX: OscHighPriThreadPool: pha.obj.throttle:notice]: PHA Obj throttled 1 times on the blob 01RootBlob-XXXXXXX in the container blobcontainer due to the "AZURE_SERVER_BUSY". Fri Aug 25 21:22:13 0000 [XXXXXXX-01: OscHighPriThreadPool: pha.obj.throttle:notice]: PHA Obj throttled 1 times on the blob XXXXXXX in the container blobcontainer due to the "AZURE_SERVER_BUSY". Fri Aug 25 21:22:15 0000 [XXXXXXXXXXXXXX: OscHighPriThreadPool: pha.obj.throttle:notice]: PHA Obj throttled 1 times on the blob preooonqp4zf in the container blobcontainer due to the "AZURE_SERVER_BUSY".Cause
Azure IO per second limit reached on Azure console :
Degraded :Throttled (CustomerInitiated)At Wednesday, 17 May 2023 at 1:22:13 am SST, the Azure monitoring system received the following information regarding your Storage account:This Storage account was throttled because it exceeded Azure Storage partition request per second , partition bandwidth,or IP scalability limits.
Recommended Steps
• To minimize impact of intermittent failures,please follow Azure Storage retry guidelines.
• If Client Throttling is happening continuously please review your partitioning setup to examine if it is preventing splitting traffic into multiple partitions.
Solution
- Increase the disk size from cloud provider end to get higher IO capacity .
- Migrate the workload from Pageblob to managed disk where higher IO capacity limit is supported .
Partner Notes
partnerNotes_text
