Skip to content

Commit da9b08f

Browse files
authored
Merge pull request #176408 from MicrosoftDocs/JasonWHowell-patch-3
Update service-fabric-stateless-node-types.md
2 parents baec02d + d3332d7 commit da9b08f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/service-fabric/service-fabric-stateless-node-types.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ To enable stateless node types, you should configure the underlying virtual mach
6868

6969
* The value **singlePlacementGroup** property, which should be set to **false** if you require to scale to more than 100 VMs.
7070
* The Scale set's **upgradeMode** should be set to **Rolling**.
71-
* Rolling Upgrade Mode requires Application Health Extension or Health probes configured. For more details on configuring the health probes or the application health extension refer to this [doc](https://docs.microsoft.com/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade#how-does-automatic-os-image-upgrade-work). Configure health probe with the default configuration for Stateless Node types as suggested below. Once the applications are deployed to the node type, Health Probe/Health extension ports can be changed to monitor the actual application health.
71+
* Rolling Upgrade Mode requires Application Health Extension or Health probes configured. For more details on configuring the health probes or the application health extension refer to this [doc](../virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md#how-does-automatic-os-image-upgrade-work). Configure health probe with the default configuration for Stateless Node types as suggested below. Once the applications are deployed to the node type, Health Probe/Health extension ports can be changed to monitor the actual application health.
7272

7373
>[!NOTE]
7474
> While using AutoScaling with Stateless node types, after scale down operation, node state is not automatically cleaned up. In order to cleanup the NodeState of Down Nodes during AutoScale, using [Service Fabric AutoScale Helper](https://github.com/Azure/service-fabric-autoscale-helper) is advised.
@@ -266,4 +266,4 @@ Once the resources have finished deploying, you can begin to disable the nodes i
266266

267267
## Next steps
268268
* [Reliable Services](service-fabric-reliable-services-introduction.md)
269-
* [Node types and virtual machine scale sets](service-fabric-cluster-nodetypes.md)
269+
* [Node types and virtual machine scale sets](service-fabric-cluster-nodetypes.md)

0 commit comments

Comments
 (0)