Cluster > Redundancy Screen - AWS Elemental Conductor Live 3

This is version 3.18 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

Cluster > Redundancy Screen

This screen shows your current redundancy setup.

Screen with No Redundancy Groups

If no redundancy groups exist, this screen appears. Your deployment may not support redundancy groups. But, if it does support redundancy groups, see the AWS Elemental Conductor Live 3 Configuration Guide for information on creating a redundancy group.


               Image file ref-cluster-no-redundancy.png

Screen for a Worker Redundancy Group

There are two types of redundancy groups: Live or Statmux (in other words, a redundancy group for worker nodes) and AWS Elemental Conductor Live 3.

The following is the Redundancy screen when a Live or Statmux redundancy group has been created:


               Image file ref-cluster-worker-redundancy.png

See the AWS Elemental Conductor Live 3 Configuration Guide.

Screen for a Conductor Redundancy Group

The following is the Redundancy screen when a Conductor redundancy group has been created.


               Image file ref-cluster-conductor-redundancy.png

Redundancy Type

Status Meaning Meaning for Initial Setup Meaning at Operation Time
0+0 No nodes (and no reserves) are in the group.

You have created a redundancy group but have not yet added nodes to it.

You must add nodes.

You still have not added nodes to the redundancy group, so the redundancy group is not going to perform any failover.
0+1 One node is in the group. It is in reserve.

You have added only one node so far and tagged it as reserve.

You must now add at least one active node.

You still have not added active nodes to the redundancy group, so the redundancy group is not going to perform any failover.
1+0 One node is in the group and it is active.

You have added only one node so far and tagged it as active.

You must now add at least one reserve node.

You still have not added reserve nodes to the redundancy group, so the redundancy group is not going to perform any failover.
0+M Multiple nodes are in the group and all are reserves. All your nodes are reserve. This is not a valid setup; assign at least one node as active. You still have not added active nodes to the redundancy group, so the redundancy group is not going to perform any failover.
1+M Multiple nodes are in the group and all nodes except one are reserves (there is only one active node). This is a valid setup if your operating procedure is to have one active node with multiple reserves. This status can happen only if your initial setup was for one active node with multiple reserves. No action is required.
N+0 Multiple nodes are in the group with no reserves. This is not a valid setup; assign at least one node as a reserve.

This status occurs if failovers have occurred and all your reserve nodes have switched to active.

An alert message is created when an N+0 redundancy type exists.

As soon as possible, you should re-assign an idle-active node to backup or bring the failed node back online. The alert will not clear until this is done.

N+1 Multiple nodes are in the group with one reserve. This is a valid setup.

This is an acceptable state to be in.

This status occurs if the initial setup has changed (some reserves have switched to active because of failover) or if you initially set up the group with only one reserve.

N+M Multiple nodes are in the group with multiple reserves. This is a valid setup.

This is an acceptable state to be in.

No action is required.

1+1 Two nodes are in the group, and one is a reserve. This is a valid setup.

This is an acceptable state to be in (the initial setup has not changed).

No action is required.