Skip to content

Commit 08517c1

Browse files
Acronis scope
1 parent 9ad6609 commit 08517c1

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/service-fabric/service-fabric-how-to-remove-node-type.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ When removing a node type that is Bronze, all the nodes in the node type go down
3131

3232
## Remove a node type
3333

34-
1. Please take care of these pre-requisites before you start the process.
34+
1. Take care of these pre-requisites before you start the process.
3535

3636
- The cluster is healthy.
37-
- There will still be sufficient capacity after the node type is removed, eg. number of nodes to place required replica count.
37+
- There will still be sufficient capacity after the node type is removed, for example, number of nodes to place required replica count.
3838

3939
2. Move all services that have placement constraints to use node type off the node type.
4040

@@ -77,7 +77,7 @@ When removing a node type that is Bronze, all the nodes in the node type go down
7777
```
7878
7979
- For bronze durability, wait for all nodes to get to disabled state
80-
- For silver and gold durability, some nodes will go in to disabled and the rest will be in disabling state. Check the details tab of the nodes in disabling state, if they are all stuck on ensuring quorum for Infrastructure service partitions, then it is safe to continue.
80+
- For silver and gold durability, some nodes go in to disabled and the rest will be in disabling state. Check the details tab of the nodes in disabling state, if they are all stuck on ensuring quorum for Infrastructure service partitions, then it is safe to continue.
8181
8282
5. Stop data for the node type.
8383
@@ -168,7 +168,7 @@ When removing a node type that is Bronze, all the nodes in the node type go down
168168
},
169169
```
170170
171-
- Deploy the modified Azure Resource Manager template. ** This step will take a while, usually up to two hours. This upgrade will change settings to the InfrastructureService, therefore a node restart is needed. In this case `forceRestart` is ignored.
171+
- Deploy the modified Azure Resource Manager template. ** This step takes a while, usually up to two hours. This upgrade change settings to the InfrastructureService, therefore a node restart is needed. In this case `forceRestart` is ignored.
172172
The parameter `upgradeReplicaSetCheckTimeout` specifies the maximum time that Service Fabric waits for a partition to be in a safe state, if not already in a safe state. Once safety checks pass for all partitions on a node, Service Fabric proceeds with the upgrade on that node.
173173
The value for the parameter `upgradeTimeout` can be reduced to 6 hours, but for maximal safety 12 hours should be used.
174174
@@ -186,8 +186,8 @@ When removing a node type that is Bronze, all the nodes in the node type go down
186186
187187
10. Remove resources relating to the node type that are no longer in use. Example Load Balancer, and Public IP.
188188
189-
- To remove these resources you can use the same PowerShell command as used in step 6 specifying the specific resource type and API version.
190-
- For silver and gold durability any repair task left in the cluster, which is targeting any of the nodes which were present in the nodetype which was removed, should be completed with the command:
189+
- To remove these resources, you can use the same PowerShell command as used in step 6 specifying the specific resource type and API version.
190+
- For silver and gold durability any repair task left in the cluster, which is targeting any of the nodes that were present in the nodetype that was removed, should be completed with the command:
191191
```powershell
192192
Complete-ServiceFabricRepairTask -TaskId <repair task name>
193193
```

0 commit comments

Comments
 (0)