Skip to content

Commit b637309

Browse files
Merge pull request #1 from meenasaravanan02/meenasaravanan02-patch-1
Updated changes to 'Cluster scale in-out'
2 parents 5acc9bf + eebd478 commit b637309

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

articles/service-fabric/service-fabric-cluster-scale-in-out.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,14 @@ Scaling compute resources to source your application work load requires intentio
2020
Virtual machine scale sets are an Azure compute resource that you can use to deploy and manage a collection of virtual machines as a set. Every node type that is defined in a Service Fabric cluster is set up as a separate virtual machine scale set. Each node type can then be scaled in or out independently, have different sets of ports open, and can have different capacity metrics. Read more about it in the [Service Fabric node types](service-fabric-cluster-nodetypes.md) document. Since the Service Fabric node types in your cluster are made of virtual machine scale sets at the backend, you need to set up auto-scale rules for each node type/virtual machine scale set.
2121

2222
> [!NOTE]
23-
> Your subscription must have enough cores to add the new VMs that make up this cluster. There is no model validation currently, so you get a deployment time failure, if any of the quota limits are hit. Also a single node type can not simply exceed 100 nodes per VMSS. You may need to add VMSS's to achieve the targeted scale, and auto-scaling can not automagically add VMSS's. Adding VMSS's in-place to a live cluster is a challenging task, and commonly this results in users provisioning new clusters with the appropriate node types provisioned at creation time; [plan cluster capacity](./service-fabric-cluster-capacity.md) accordingly.
24-
>
25-
>
23+
> Your subscription must have enough cores to add the new VMs that make up this cluster. There is no model validation currently, so you get a deployment time failure, if any of the quota limits are hit.
24+
>
25+
>
26+
> [!NOTE]
27+
> If using an OS Image "-with-containers” memory metrics from Azure Monitor will not be available.
28+
>
29+
>
30+
2631

2732
## Choose the node type/Virtual Machine scale set to scale
2833
Currently, you are not able to specify the auto-scale rules for virtual machine scale sets using the portal to create a Service Fabric Cluster, so let us use Azure PowerShell (1.0+) to list the node types and then add auto-scale rules to them.

0 commit comments

Comments
 (0)