You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machine-scale-sets/standby-pools-faq.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,22 +20,22 @@ Get answers to frequently asked questions about standby pools for Virtual Machin
20
20
Azure standby pools is a feature for Virtual Machine Scale Sets with Flexible Orchestration that enables faster scaling out of resources by creating a pool of pre-provisioned virtual machines ready to service your workload.
21
21
22
22
### When should I use standby pools for Virtual Machine Scale Sets?
23
-
Using a standby pool with your Virtual Machine Scale Set can help improve scaleout performance by completing various pre and post provisioning steps in the pool before the instances are placed into the scale set.
23
+
Using a standby pool with your Virtual Machine Scale Set can help improve scale-out performance by completing various pre and post provisioning steps in the pool before the instances are placed into the scale set.
24
24
25
25
### What are the benefits of using Azure standby pools for Virtual Machine Scale Sets?
26
-
Standby pools is a powerful feature for accelerating your time to scaleout and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf.
26
+
Standby pools is a powerful feature for accelerating your time to scale-out and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf.
27
27
28
28
### Can I use standby pools on Virtual Machine Scale Sets with Uniform Orchestration?
29
-
No. Standby pools is only supported on Virtual Machine Scale Sets with Flexible Orchestration.
29
+
Standby pools is only supported on Virtual Machine Scale Sets with Flexible Orchestration.
30
30
31
31
### Can I use standby pools for Virtual Machine Scale Sets if I'm already using Azure autoscale?
32
-
No. Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled is not supported.
32
+
Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled isn't supported.
33
33
34
34
### How many virtual machines can my standby pool for Virtual Machine Scale Sets have?
35
35
The maximum number of virtual machines between a scale set and a standby pool is 1,000.
36
36
37
37
### Can my standby pool span multiple Virtual Machine Scale Sets?
38
-
No. A standby pool resource can't span multiple scale sets. Each scale set has its own standby pool attached to it. A standby pool inherits the unique properties of the scale set such as networking, virtual machine profile, extensions, and more.
38
+
A standby pool resource can't span multiple scale sets. Each scale set has its own standby pool attached to it. A standby pool inherits the unique properties of the scale set such as networking, virtual machine profile, extensions, and more.
39
39
40
40
### How is the configuration of my virtual machines in the standby pool for Virtual Machine Scale Sets determined?
41
41
Virtual machines in the standby pool inherit the same virtual machine profile as the virtual machines in the scale set. Some examples are:
@@ -55,8 +55,8 @@ Yes. To change the size of your standby pool update the max ready capacity setti
55
55
### I created a standby pool and I noticed that some virtual machines are coming up in a failed state.
56
56
Ensure you have enough quota to complete the standby pool creation. Insufficient quota results in the platform attempting to create the virtual machines in the standby pool but unable to successfully complete the create operation. Check for multiple types of quotas such as Cores, Network Interfaces, IP Addresses, etc.
57
57
58
-
### I increased my scale set instance count but the virtual machines in my standby pool were not used.
59
-
Ensure that the virtual machines in your standby pool are in the desired state prior to attempting a scaleout event. For example, if using a standby pool with the virtual machine state set to deallocated, the standby pool will only give out instances that are in the deallocated state. If instances are in any other state such as creating, running, updating, etc, the scale set will default to net new virtual machine creation.
58
+
### I increased my scale set instance count but the virtual machines in my standby pool weren't used.
59
+
Ensure that the virtual machines in your standby pool are in the desired state prior to attempting a scale-out event. For example, if using a standby pool with the virtual machine states set to deallocated, the standby pool will only give out instances that are in the deallocated state. If instances are in any other states such as creating, running, updating, etc., the scale set will default to net new virtual machine creation.
0 commit comments