Page tree
Skip to end of metadata
Go to start of metadata

This page describes how to upgrade ClustrixDB. If you have any questions, please contact Clustrix Support.

As of version 9, ClustrixDB supports RHEL/CentOS 7 and non-root user operation. For optimal performance and security Clustrix recommends utilizing this configuration. Non-root and OS changes require a fresh installation of ClustrixDB.

Prerequisites:

  1. All nodes must be online. The output of clx stat should indicate a cluster status of OK.
  2. Confirm that the upgrade package you have is compatible with your current version of ClustrixDB, including the OS version.

  3. Review the list of Upgrade Alerts included in the Release Notes. 
  4. All upgrades should be run as the ClustrixDB daemon user (clxd)
  5. Passwordless SSH authentication must be configured for the ClustrixDB daemon user (clxd). To verify this, confirm that the clx command returns successfully with no passwords requested: 

    shell> /opt/clustrix/bin/clx cmd 'date'  

    See Configuring SSH Authentication.

  6. Ensure that the clocks are synchronized between nodes. For instructions on syncing the clocks between nodes, see the Verify NTP is running on ClustrixDB.

To upgrade:

All ClustrixDB upgrade packages will upgrade the database and ClustrixGUI. The upgrader should be run from a single node and will upgrade all nodes in the cluster. ClustrixDB does not support downgrades.

Performing an upgrade will incur a short period of downtime.

  1. Download the upgrade package to a single node 

  2. (Optional) if you are using a non-default ssh port, set an environment variable 

    shell> export ssh_port_number
  3. Run the upgrader as the database daemon user (e.g. clxd). If the database has been installed with root users only, then run the upgrader as root. 

    shell> sudo -u clxd bash ./clustrix-clxnode-version-upgrade.sh install       

    This will upgrade every node in the cluster. While the upgrade is in progress, there is a brief period during which the database is unavailable.

Once the database portion of the upgrade is complete, the cluster is online. The UI portion of the upgrade will continue but the database is available. 

  • No labels