Step E: Re-enable High Availability on the AWS Elemental Conductor File Nodes - AWS Elemental Conductor File

This is version 2.16 of the AWS Elemental Conductor File documentation. This is the latest version. For prior versions, see the Archive section of AWS Elemental Conductor File and AWS Elemental Server Documentation.

Step E: Re-enable High Availability on the AWS Elemental Conductor File Nodes

If you have only one Conductor File node, skip to Step F: Downgrade the Worker Nodes.

You must re-enable high availability on the Conductor nodes, to put the nodes back into a redundant configuration.

To enable high availability on the primary Conductor

  1. From the Linux prompt, log in to the primary Conductor node with the elemental user credentials.

  2. Enter the following command to configure the primary Conductor node for high availability. 

    [elemental@hostname ~]$ sudo /opt/elemental_se/.support_utils/dbrepl configure <dbrepl_config_file_name> primary

    Where <dbrepl_config_file_name> is your dbrepl_config.yml file.

  3. Restart the elemental_se service.

    [elemental@hostname ~]$ sudo /etc/init.d/elemental_se restart

  4. Enter the following command to verify that the service is running.

    [elemental@hostname ~]$ tail -F /opt/elemental_se/web/log/conductor.output

    The conductor.output log starts to scroll on the screen and shows messages as they are occurring. Watch for the following three INFO lines on the primary Conductor node. 

    CONDUCTOR: Initializing environment
I, [2015-11-13T04:37:54.491204 #4978]  INFO -- : Configuring the HA environment
I, [2015-11-13T04:37:54.660644 #4978]  INFO -- : configuring keepalived
I, [2015-11-13T04:38:03.905069 #4978]  INFO -- : Preparing database as replication master
[2015-11-13 04:39:03 UTC SERVICE]: Elemental Conductor File 2.16.x.x

  5. Type Ctrl-C to exit the tail command.

  6. Enter the following commands.

    [elemental@hostname ~]$ sudo -s 
    [elemental@hostname ~]$ cd /data/pgsql/logs
    [elemental@hostname ~]$ tail -F postgresql-<day>.log

    Where <day> is today (the day you are upgrading), typed with an initial capital letter: Mon, Tue, Wed, Thu, Fri, Sat, Sun

  7. Confirm that you see this line.

    database system is ready to accept connections.
    Note

    If the elemental_se or postgres process has already started when you starting tailing the logs, you might not see the ready to accept connections message. Instead, you could see rejects connection for host messages until you upgrade the worker nodes.

  8. Enter Ctrl-C to exit the tail command.

  9. Type the following command to exit the session as the sudo user.

    [elemental@hostname ~]$ exit

On the secondary Conductor

Repeat high availability steps on the secondary Conductor but use the following command instead. 

[elemental@hostname ~]$ sudo /opt/elemental_se/.support_utils/dbrepl configure <dbrepl_config_file_name> secondary