This is version 2.3 of the AWS Elemental Delta documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Delta Documentation.
Step H: Test Fail Over
To ensure the leader and secondary node fail over works as expected, test the fail over setup.
To test fail over
-
Ideally, you should add at least one input so that AWS Elemental Delta is ingesting content. This setup provides a better test of the success of the failover.
-
Perform a forced failover to the secondary leader (node B):
-
On the web interface for the leader node, choose Nodes.
-
On the panel for the secondary node, click the fail over button (family tree icon).
-
-
Make sure the panels for both nodes show as green.
-
Make sure that node B shows N/A (node is leader) in the following fields:
-
Following Node ID
-
Replication Lag
-
Last Heartbeat
-
-
Display the Contents page and make sure that the content you created shows as Live-Active.
-
Make sure that node A shows the following:
-
Following Node ID: The node ID for node B.
-
Replication Lag: A number below 10 seconds.
-
Last Heartbeat: A number below 10 seconds.
-
-
Perform a forced fail over back to node A. Make sure that node A becomes the leader again and the content is still active.