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-azure-resource-manager-guardrails.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,17 +63,17 @@ To fix a durability mismatch, which is indicated by any of the above error messa
63
63
64
64
## Seed Node Deletion
65
65
### Overview
66
-
A Service Fabric cluster has a [reliability tier](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-capacity#the-reliability-characteristics-of-the-cluster) property which is used to determine the number of replicas of system services that run on the primary node type of the cluster. The number of replicas determines the minimum number of nodes that must be maintained in the primary node type of the cluster. If the number of nodes in this primary node type goes below this minimum the cluster will become unstable.
66
+
A Service Fabric cluster has a [reliability tier](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-capacity#the-reliability-characteristics-of-the-cluster) property which is used to determine the number of replicas of system services that run on the primary node type of the cluster. The number of required replicas will determine the minimum number of nodes that must be maintained in the primary node type of the cluster. If the number of nodes in the primary node type goes below the required minimum for the reliability tier, the cluster will become unstable.
67
67
68
68
### Error Messages
69
69
Seed node removal operation has been detected, and will be rejected.
70
70
* This operation would result in only {0} potential seed nodes to remain in the cluster, while {1} are needed as a minimum.
71
71
* Removing {0} seed nodes out of {1} would result in the cluster going down due to loss of seed node quorum. Maximum number of seed nodes that can be removed at a time is {2}.
72
72
73
73
### Mitigation
74
-
Ensure that your primary node type has enough virtual machines for the reliability tier that is 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 nodes required for the given reliability tier.
75
-
* If the reliability tier is correctly specified, make sure that you have enough Virtual Machines as needed for the reliability tier.
76
-
* If the reliability tier is incorrect, initiate a change on the Service Fabric resource to lower reliability level first before initiating any Virtual Machine Scale Set operations, and let it complete.
74
+
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.
75
+
* 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.
76
+
* 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
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.
0 commit comments