Skip to content

Commit 6c4eb20

Browse files
authored
Update service-fabric-best-practices-capacity-scaling.md
1 parent 602e237 commit 6c4eb20

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/service-fabric/service-fabric-best-practices-capacity-scaling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In addition to considering node type and cluster characteristics, you should exp
2525
## Autoscaling
2626
You should perform scaling operations via Azure Resource Manager templates, because it's the best practice to treat [resource configurations as code]( https://docs.microsoft.com/azure/service-fabric/service-fabric-best-practices-infrastructure-as-code).
2727

28-
Using automatic scaling through virtual machine scale sets will make your versioned Resource Manager template inaccurately define your instance counts for virtual machine scale sets. Inaccurate definition increases the risk that future deployments will cause unintended scaling operations. In general, you should use auto scaling if:
28+
Using automatic scaling through virtual machine scale sets will make your versioned Resource Manager template inaccurately define your instance counts for virtual machine scale sets. Inaccurate definition increases the risk that future deployments will cause unintended scaling operations. In general, you should use autoscaling if:
2929

3030
* Deploying your Resource Manager templates with appropriate capacity declared doesn’t support your use case.
3131

0 commit comments

Comments
 (0)