Step I: Review the Cluster Management Configuration - AWS Elemental Delta

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 I: Review the Cluster Management Configuration

To ensure the leader and secondary node fail over is appropriate for your workflow, review the configuration of your cluster management settings.

To review the management configuration

  1. Access the web interface via the VIP address for the management interface (eth0).

  2. On the main menu, click Nodes.

  3. Check the values of the fields across the top:

    Field Description
    Heartbeat Interval A heartbeat is sent between the leader and secondary nodes. The secondary node uses the presence or failure of this heartbeat to assume that the leader is (or is not) working.
    Cluster-Mgr Interval The interval (in seconds) for performing cluster management tasks such as checking for node timeouts.
    Drop Node After If it is detected that the leader node has failed (the heartbeat is not received by the secondary node), activity fails over to the secondary node after this many seconds.
    Take Action Time

    The number of seconds to wait after a fail over has occurred before allowing another fail over. This delay ensures that in a fail over, the new leader node has had time to completely gain control of the cluster.

    For example, if node A fails and node B becomes leader and this delay is too short, the system might detect that node B has failed. However, node B might not yet be completely responsive because it is still setting itself up as leader.
    Healthz Replication Delay Leave the default; this feature is not used because you do not have a load balancer.

  4. To change any values, click Settings in the top-right corner and make your changes.