Step D: Disable 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 D: Disable High Availability on the AWS Elemental Conductor File Nodes

Disable high availability prior to performing any changes on the Conductor nodes.

To disable 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 HA.

    [elemental@hostname ~]$ sudo /opt/elemental_se/.support_utils/dbrepl disable
  3. Restart the service using the following commands.

    [elemental@hostname ~]$ sudo /etc/init.d/postgresql-9.4 restart [elemental@hostname ~]$ sudo /etc/init.d/elemental_se restart
  4. Enter the following command to verify that Conductor high availability is disabled.

    [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 INFO lines on the primary Conductor node.

    CONDUCTOR: Initializing environment I, [2015-11-13T04:37:54.491204 #4978]  INFO -- : HA environment not enabled [2015-11-13 04:39:03 UTC SERVICE]: Elemental Conductor File 2.15.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. Type Ctrl-C to exit the tail command.

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

    [elemental@hostname ~]$ exit

To disable high availability on the secondary Conductor

Repeat the high-availability steps on the secondary Conductor node, logged into the secondary Conductor node.