Large MCS deployments in Azure may fail due to Azure throttling of disk clones
book
Article ID: CTX491278
calendar_today
Updated On:
Description
Customers hosting VMs in Azure may experience an error when attempting to create a large machine catalog or add additional machines in bulk, resulting in failure to create new machines. This error will appear in Azure as:
"Too many attempts to copy from a writable resource (a managed disk); please use a snapshot source to create many copies in a short time."
Resolution
- Up-to 49 disks can be created concurrently. For now, Azure suggests that customers use shared image gallery as the source for deployments at scale.
Problem Cause
OS disks of Trusted VMs have an accompanying storage object for the TPM state of the VM. Some of the Azure scalability enhancements, for creating number of OS disks from a Snapshot in quick succession, haven’t been implemented for the TPM state of Trusted VM OS disks. Azure has identified repair items based on how they handle Non-TVM disk creation at scale and extend same optimizations to TVM disks to offer greater concurrent limits.
Issue/Introduction
Large MCS deployments in Azure may fail due to Azure throttling of disk clones. "Too many attempts to copy from a writable resource (a managed disk); please use a snapshot source to create many copies in a short time."
Was this article helpful?
thumb_up
Yes
thumb_down
No