AWS elemental-cl3 documentation change
Summary
Updated failover behavior description to state that recovered primary Conductor node regains leadership
Security assessment
Operational change in failover behavior with no direct security impact. Focuses on high availability mechanics.
Diff
diff --git a/elemental-cl3/latest/ug/monitoring-conductor-and-worker-nodes.md b/elemental-cl3/latest/ug/monitoring-conductor-and-worker-nodes.md index 9011f8b72..29aac3b98 100644 --- a//elemental-cl3/latest/ug/monitoring-conductor-and-worker-nodes.md +++ b//elemental-cl3/latest/ug/monitoring-conductor-and-worker-nodes.md @@ -170 +170 @@ When worker redundancy is not implemented on the cluster and a worker node has f -When you have redundant Conductor Live nodes set up, then, when the primary fails, the backup automatically takes over management of the cluster. This change in role takes a few seconds. +When you have redundant Conductor Live nodes set up and the primary node fails, the secondart node automatically takes over management of the cluster. This change in role takes a few seconds. @@ -172,7 +172 @@ When you have redundant Conductor Live nodes set up, then, when the primary fail -After failover has occurred, the two Conductor Live nodes continue in their new roles. - -Even when the failed Conductor Live comes back online, it does not take back the leader role: it comes back into service as the backup. - -###### Note - -Typically, there is no reason for you to switch back to the node that was previously the primary: there is no need to prefer one Conductor node as the primary for the other. In fact, there is no mechanism for you to switch the node roles. +If you resolve the problem with the failed primary Conductor Live node and bring it back into the cluster, that primary node will take back the leadership role from the secondary Conductor Live node.