Skip to content

Commit 9eb4a0b

Browse files
committed
update images
1 parent ba71348 commit 9eb4a0b

4 files changed

Lines changed: 2 additions & 272 deletions

File tree

support/azure/virtual-machines/windows/allocation-failure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -228,12 +228,12 @@ Reduce the number of instances of the requested VM size, and then retry the depl
228228

229229
The servers in Azure datacenters are partitioned into clusters. Normally, an allocation request is attempted in multiple clusters, but it's possible that certain constraints (such as VM size, Ultra SSD, and proximity placement groups) from the allocation request force the Azure platform to attempt the request in only one cluster. Diagram 1 below illustrates the case of a normal allocation that is attempted in multiple clusters.
230230

231-
:::image type="content" source="media/virtual-machines-common-allocation-failure/how-allocation-works.svg" alt-text="Diagram 1 shows allocation attempted in multiple clusters and Diagram 2 shows allocation pinned to one cluster." lightbox="media/virtual-machines-common-allocation-failure/how-allocation-works.svg":::
231+
:::image type="content" source="media/virtual-machines-common-allocation-failure/how-allocation-works.png" alt-text="Diagram 1 shows allocation attempted in multiple clusters." lightbox="media/virtual-machines-common-allocation-failure/how-allocation-works.png":::
232232

233233
### Why allocation failures happen
234234

235235
When an allocation has a high number of restrictions, there's a higher chance of failing to find free resources since the available resource pool is smaller. Furthermore, if your allocation request is restricted, such as when using proximity placement groups but the type of resource you requested isn’t supported by the set of clusters and nearby ones, your request will fail even if the cluster has free resources. The following Diagram 2 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don't have free resources. Diagram 3 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don’t support the requested VM size, even though the clusters have free resources.
236236

237-
:::image type="content" source="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.svg" alt-text="Diagram 3 shows allocation failed at pinned cluster: No free resource available and Diagram 4 shows allocation failed at pinned cluster: Size not supported." lightbox="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.svg":::
237+
:::image type="content" source="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png" alt-text="Diagram 2 shows allocation failed with no free resource available and Diagram 3 shows allocation failed with size not supported." lightbox="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png":::
238238

239239
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/virtual-machines/windows/media/virtual-machines-common-allocation-failure/allocation-failures-ppg.svg renamed to support/azure/virtual-machines/windows/media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png

File renamed without changes.
-30.3 KB
Loading

support/azure/virtual-machines/windows/media/virtual-machines-common-allocation-failure/how-allocation-works.svg

Lines changed: 0 additions & 270 deletions
This file was deleted.

0 commit comments

Comments
 (0)