Updated automatic-failover.adoc

supritha-kumar · ggray-cb · commit 04bea996029b · 2025-08-26T15:50:47.000-04:00
made a change on 7.6 by mistake and re-did it.
I had changed "the failure of one of the nodes" to "the failure of some of the nodes".

Have changed it back to "one of the nodes"
diff --git a/modules/learn/pages/clusters-and-availability/automatic-failover.adoc b/modules/learn/pages/clusters-and-availability/automatic-failover.adoc
@@ -75,7 +75,7 @@ Another critical auto-failover constraint for Server Groups is the maximum numbe
 
 The list below describes other conditions that must be met for an auto-failover to be executed even after a monitored or configured auto-failover event has occurred.
 
-* If the majority of nodes in the cluster can form a quorum to initiate failover, following the failure of some of the nodes.
+* If the majority of nodes in the cluster can form a quorum to initiate failover, following the failure of one of the nodes.
 For example, given a cluster of 18 nodes, _10_ nodes are required for the quorum; and given a cluster of 17 nodes, _9_ nodes are required for the quorum.
 ** In the event of certain disk read/write issues it is important to also consider the efficacy of the nodes in the cluster. Should a node encounter such an issue, particularly an issue causing extreme disk slowness, and the disk encountering the issue is shared between the Data Service and the Cluster Manager, then this node is unlikely to be able to participate in this quorum. The idea of a quorum should be extended beyond “nodes that can communicate with one another” to “nodes that can communicate with one another and and can reliably read from, and write to, their respective disks”.
 +

Original file line number	Diff line number	Diff line change
`@@ -75,7 +75,7 @@ Another critical auto-failover constraint for Server Groups is the maximum numbe`
`75`	`75`
`76`	`76`	`The list below describes other conditions that must be met for an auto-failover to be executed even after a monitored or configured auto-failover event has occurred.`
`77`	`77`
`78`		`-* If the majority of nodes in the cluster can form a quorum to initiate failover, following the failure of some of the nodes.`
	`78`	`+* If the majority of nodes in the cluster can form a quorum to initiate failover, following the failure of one of the nodes.`
`79`	`79`	`For example, given a cluster of 18 nodes, _10_ nodes are required for the quorum; and given a cluster of 17 nodes, _9_ nodes are required for the quorum.`
`80`	`80`	** In the event of certain disk read/write issues it is important to also consider the efficacy of the nodes in the cluster. Should a node encounter such an issue, particularly an issue causing extreme disk slowness, and the disk encountering the issue is shared between the Data Service and the Cluster Manager, then this node is unlikely to be able to participate in this quorum. The idea of a quorum should be extended beyond “nodes that can communicate with one another” to “nodes that can communicate with one another and and can reliably read from, and write to, their respective disks”.
`81`	`81`	`+`