You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-how-to-remove-node-type.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,10 +31,10 @@ When removing a node type that is Bronze, all the nodes in the node type go down
31
31
32
32
## Remove a node type
33
33
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.
35
35
36
36
- 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.
38
38
39
39
2. Move all services that have placement constraints to use node type off the node type.
40
40
@@ -77,7 +77,7 @@ When removing a node type that is Bronze, all the nodes in the node type go down
77
77
```
78
78
79
79
- 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.
81
81
82
82
5. Stop data for the node type.
83
83
@@ -168,7 +168,7 @@ When removing a node type that is Bronze, all the nodes in the node type go down
168
168
},
169
169
```
170
170
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.
172
172
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.
173
173
The value for the parameter `upgradeTimeout` can be reduced to 6 hours, but for maximal safety 12 hours should be used.
174
174
@@ -186,8 +186,8 @@ When removing a node type that is Bronze, all the nodes in the node type go down
186
186
187
187
10. Remove resources relating to the node type that are no longer in use. Example Load Balancer, and Public IP.
188
188
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:
0 commit comments