Skip to content

Commit 0e5fabc

Browse files
committed
Update links to renamed file
1 parent 2292c0d commit 0e5fabc

15 files changed

+19
-19
lines changed

articles/service-fabric/service-fabric-azure-resource-manager-guardrails.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Seed node removal operation has been detected, and will be rejected.
7474
Ensure that your primary node type has enough Virtual Machines for the reliability specified on your cluster. You will not be able to remove a Virtual Machine if it will bring the Virtual Machine Scale Set below the minimum number of nodes for the given reliability tier.
7575
* If the reliability tier is correctly specified, make sure that you have enough nodes in the primary node type as needed for the reliability tier.
7676
* If the reliability tier is incorrect, initiate a change on the Service Fabric resource to lower the reliability level first before initiating any Virtual Machine Scale Set operations, and wait for it to complete.
77-
* If the reliability tier is Bronze, please follow these [steps](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-up-down#manually-remove-vms-from-a-node-typevirtual-machine-scale-set) to scale down your cluster gracefully.
77+
* If the reliability tier is Bronze, please follow these [steps](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-in-out#manually-remove-vms-from-a-node-typevirtual-machine-scale-set) to scale in your cluster gracefully.
7878

7979
## Next steps
8080
* Create a cluster on VMs or computers running Windows Server: [Service Fabric cluster creation for Windows Server](service-fabric-cluster-creation-for-windows-server.md)

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ With the node properties and placement constraints declared, do the following st
7070

7171
## Horizontal scaling
7272

73-
You can do horizontal scaling either [manually](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-up-down) or [programmatically](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-programmatic-scaling).
73+
You can do horizontal scaling either [manually](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-in-out) or [programmatically](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-programmatic-scaling).
7474

7575
> [!NOTE]
7676
> If you're scaling a node type that has Silver or Gold durability, scaling will be slow.
@@ -162,7 +162,7 @@ scaleSet.Update().WithCapacity(newCapacity).Apply();
162162
```
163163

164164
> [!NOTE]
165-
> When you scale down a cluster, you'll see the removed node/VM instance displayed in an unhealthy state in Service Fabric Explorer. For an explanation of this behavior, see [Behaviors you may observe in Service Fabric Explorer](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-up-down#behaviors-you-may-observe-in-service-fabric-explorer). You can:
165+
> When you scale down a cluster, you'll see the removed node/VM instance displayed in an unhealthy state in Service Fabric Explorer. For an explanation of this behavior, see [Behaviors you may observe in Service Fabric Explorer](https://docs.microsoft.com/azure/service-fabric/service-fabric-cluster-scale-in-out#behaviors-you-may-observe-in-service-fabric-explorer). You can:
166166
> * Call the [Remove-ServiceFabricNodeState command](https://docs.microsoft.com/powershell/module/servicefabric/remove-servicefabricnodestate?view=azureservicefabricps) with the appropriate node name.
167167
> * Deploy the [Service Fabric autoscale helper application](https://github.com/Azure/service-fabric-autoscale-helper/) on your cluster. This application ensures that the scaled-down nodes are cleared from Service Fabric Explorer.
168168

articles/service-fabric/service-fabric-cluster-config-upgrade-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,4 +48,4 @@ You can also customize cluster settings in one of the following ways with Azure
4848

4949
## Next steps
5050
* Learn about the [Service Fabric cluster settings](service-fabric-cluster-fabric-settings.md).
51-
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-up-down.md).
51+
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-in-out.md).

articles/service-fabric/service-fabric-cluster-config-upgrade-windows-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Four options are supported:
7070

7171
## Next steps
7272
* Learn how to customize some [Service Fabric cluster settings](service-fabric-cluster-fabric-settings.md).
73-
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-up-down.md).
73+
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-in-out.md).
7474
* Learn about [application upgrades](service-fabric-application-upgrade.md).
7575

7676
<!--Image references-->

articles/service-fabric/service-fabric-cluster-programmatic-scaling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: mikerou
1010

1111
# Scale a Service Fabric cluster programmatically
1212

13-
Service Fabric clusters running in Azure are built on top of virtual machine scale sets. [Cluster scaling](./service-fabric-cluster-scale-up-down.md) describes how Service Fabric clusters can be scaled either manually or with auto-scale rules. This article describes how to manage credentials and scale a cluster in or out using the fluent Azure compute SDK, which is a more advanced scenario. For an overview, read [programmatic methods of coordinating Azure scaling operations](service-fabric-cluster-scaling.md#programmatic-scaling).
13+
Service Fabric clusters running in Azure are built on top of virtual machine scale sets. [Cluster scaling](./service-fabric-cluster-scale-in-out.md) describes how Service Fabric clusters can be scaled either manually or with auto-scale rules. This article describes how to manage credentials and scale a cluster in or out using the fluent Azure compute SDK, which is a more advanced scenario. For an overview, read [programmatic methods of coordinating Azure scaling operations](service-fabric-cluster-scaling.md#programmatic-scaling).
1414

1515

1616
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
@@ -115,6 +115,6 @@ await client.ClusterManager.RemoveNodeStateAsync(mostRecentLiveNode.NodeName);
115115

116116
To get started implementing your own auto-scaling logic, familiarize yourself with the following concepts and useful APIs:
117117

118-
- [Scaling manually or with auto-scale rules](./service-fabric-cluster-scale-up-down.md)
118+
- [Scaling manually or with auto-scale rules](./service-fabric-cluster-scale-in-out.md)
119119
- [Fluent Azure Management Libraries for .NET](https://github.com/Azure/azure-sdk-for-net/tree/Fluent) (useful for interacting with a Service Fabric cluster's underlying virtual machine scale sets)
120120
- [System.Fabric.FabricClient](https://docs.microsoft.com/dotnet/api/system.fabric.fabricclient) (useful for interacting with a Service Fabric cluster and its nodes)

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -250,7 +250,7 @@ Read the following to also learn about planning cluster capacity, upgrading a cl
250250
* [Partition stateful services for maximum scale](service-fabric-concepts-partitioning.md)
251251

252252
<!--Image references-->
253-
[BrowseServiceFabricClusterResource]: ./media/service-fabric-cluster-scale-up-down/BrowseServiceFabricClusterResource.png
254-
[ClusterResources]: ./media/service-fabric-cluster-scale-up-down/ClusterResources.png
253+
[BrowseServiceFabricClusterResource]: ./media/service-fabric-cluster-scale-in-out/BrowseServiceFabricClusterResource.png
254+
[ClusterResources]: ./media/service-fabric-cluster-scale-in-out/ClusterResources.png
255255

256256
[durability]: service-fabric-cluster-capacity.md#the-durability-characteristics-of-the-cluster

articles/service-fabric/service-fabric-cluster-scaling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,10 +27,10 @@ When scaling an Azure cluster, keep the following guidelines in mind:
2727
- Do not remove random VM instances/nodes from a node type, always use the virtual machine scale set scale down feature. The deletion of random VM instances can adversely affect the systems ability to properly load balance.
2828
- If using autoscale rules, set the rules so that scaling in (removing VM instances) is done one node at a time. Scaling down more than one instance at a time is not safe.
2929

30-
Since the Service Fabric node types in your cluster are made up of virtual machine scale sets at the backend, you can [set up auto-scale rules or manually scale](service-fabric-cluster-scale-up-down.md) each node type/virtual machine scale set.
30+
Since the Service Fabric node types in your cluster are made up of virtual machine scale sets at the backend, you can [set up auto-scale rules or manually scale](service-fabric-cluster-scale-in-out.md) each node type/virtual machine scale set.
3131

3232
### Programmatic scaling
33-
In many scenarios, [Scaling a cluster manually or with autoscale rules](service-fabric-cluster-scale-up-down.md) are good solutions. For more advanced scenarios, though, they may not be the right fit. Potential drawbacks to these approaches include:
33+
In many scenarios, [Scaling a cluster manually or with autoscale rules](service-fabric-cluster-scale-in-out.md) are good solutions. For more advanced scenarios, though, they may not be the right fit. Potential drawbacks to these approaches include:
3434

3535
- Manually scaling requires you to sign in and explicitly request scaling operations. If scaling operations are required frequently or at unpredictable times, this approach may not be a good solution.
3636
- When auto-scale rules remove an instance from a virtual machine scale set, they do not automatically remove knowledge of that node from the associated Service Fabric cluster unless the node type has a durability level of Silver or Gold. Because auto-scale rules work at the scale set level (rather than at the Service Fabric level), auto-scale rules can remove Service Fabric nodes without shutting them down gracefully. This rude node removal will leave 'ghost' Service Fabric node state behind after scale-in operations. An individual (or a service) would need to periodically clean up removed node state in the Service Fabric cluster.

articles/service-fabric/service-fabric-cluster-upgrade-standalone.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The patch orchestration application (POA) is a Service Fabric application that a
3333

3434
## Next steps
3535
* Learn how to customize some of the [service fabric cluster fabric settings](service-fabric-cluster-fabric-settings.md)
36-
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-up-down.md)
36+
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-in-out.md)
3737
* Learn about [application upgrades](service-fabric-application-upgrade.md)
3838

3939
<!--Image references-->

articles/service-fabric/service-fabric-cluster-upgrade-version-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ Output:
106106

107107
## Next steps
108108
* Learn how to customize some of the [service fabric cluster fabric settings](service-fabric-cluster-fabric-settings.md)
109-
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-up-down.md)
109+
* Learn how to [scale your cluster in and out](service-fabric-cluster-scale-in-out.md)
110110
* Learn about [application upgrades](service-fabric-application-upgrade.md)
111111

112112
<!--Image references-->

articles/service-fabric/service-fabric-cluster-upgrade-windows-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ For usage details, see the [Start-ServiceFabricClusterConfigurationUpgrade](http
158158
## Next steps
159159
* [Upgrade the configuration of a standalone cluster](service-fabric-cluster-config-upgrade-windows-server.md)
160160
* Customize some [Service Fabric cluster settings](service-fabric-cluster-fabric-settings.md).
161-
* [Scale your cluster in and out](service-fabric-cluster-scale-up-down.md).
161+
* [Scale your cluster in and out](service-fabric-cluster-scale-in-out.md).
162162
163163
<!--Image references-->
164164
[getfabversions]: ./media/service-fabric-cluster-upgrade-windows-server/getfabversions.PNG

0 commit comments

Comments
 (0)