Skip to content

Commit 451f26e

Browse files
author
Chacko Daniel
authored
Fixing the warning
1 parent 70a0153 commit 451f26e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/service-fabric/virtual-machine-scale-set-scale-node-type-scale-out.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ This article describes how to scale an Azure Service Fabric cluster by adding a
2222

2323
> [!WARNING]
2424
>
25-
Do not start to change the primary nodetype VM SKU process, if the cluster health is unhealthy. If the cluster health is unhealthy, you will only destabilize the cluster if you try to change the VM SKU.
25+
Do not start to change the primary nodetype VM SKU, if the cluster health is unhealthy. If the cluster health is unhealthy, you will only destabilize the cluster further, if you try to change the VM SKU.
2626

2727
We recommend that you do not change the VM SKU of a scale set/node type unless it is running at [Silver durability or greater](service-fabric-cluster-capacity.md#the-durability-characteristics-of-the-cluster). Changing VM SKU Size is a data-destructive in-place infrastructure operation. Without some ability to delay or monitor this change, it is possible that the operation can cause data loss for stateful services or cause other unforeseen operational issues, even for stateless workloads. This means your primary node type, which is running stateful service fabric system services, or any node type that is running your stateful application work loads.
2828
>

0 commit comments

Comments
 (0)