Updating the Distributed DDNS Data Node and database cluster - Adaptive Applications - BlueCat Gateway - 22.1

BlueCat Distributed DDNS Administration Guide

Locale
English (United States)
Product name
BlueCat Gateway
Version
22.1

Updating the Distributed DDNS Data Node database cluster allows you to take advantage of new features, while maintaining support of your DDNS Data Node database cluster software. Performing a rolling update can be time consuming, depending on the size of the database and the number of nodes that exist in the cluster. During the database update, the cluster operates at a reduced capacity while nodes update.

Once you have upgraded the Distributed DDNS Application Node to v22.1, you can use the DDNS Deployment page to upgrade the other components.



  • Switch DB—displays a list of all current database nodes in the clusters as IP addresses. The list can take up to two minutes to populate when selected. You can perform the following actions:
    • Display which database node that the application node is currently connected to.
    • Switch the database connection of the application node to a different database node.
  • —displays whether a new version of database node software is available for upgrade. The application node polls the node for the current software version to determine whether an updated version is available.
  • —displays whether a new version of service node software is available for upgrade. The application node polls the node for the current software version to determine whether an updated version is available.
  • —the application node cannot connect to the service node or database node.

Performing a rolling update of the database cluster

  1. Click the next to the database node that you would like to upgrade. The Upgrade Database Node window opens.
  2. Within the Authentication section, select either Password or SSH and provide the corresponding authentication information.
  3. Under Repository, enter the following information:
    • Image: enter the default URL for the database Docker image
    • User and Password: enter your Quay or local repository username and password.
  4. Click Upgrade.
During the upgrade process, the system performs checks and periodically asks you to confirm the following information:
  • Check for the current status of the database nodes in the database cluster, such as the total number of nodes and number of primary nodes.
  • Check for the external client connections to the database node and show all client IP addresses.
  • Check for the internal connections within the database node and display their process IDs.

The upgrade process displays any errors reported and successful messages. Once the node has successfully installed the updated software, you can verify the upgrade status from the Database Nodes page. Verify that the node has successfully joined the cluster and has synchronized by checking the MariaDB service logs. For more information, refer to Configuring MariaDB service.

If the node updated successfully and reconnected to the cluster, you can proceed to update the next node in the cluster.

After the upgrade

  • Check the log files on the Distributed DDNS Application Node to verify that the update was successful. In particular, check the log of the MariaDB service on the DDNS Application.
  • Check the status of the Auto Backup, Auto Scavenge, and Sync Data daemons on the updated Distributed DDNS Application Node. If the daemons do not start automatically on any data node, start them on any node in the cluster. The daemons only need to run on one of the Data Nodes in the cluster.

Performing a database schema update

Before you proceed to update the database schema, you must first update the database software. You can update the schema on any node of the database cluster. Once the schema has been updated on one node, the remaining nodes in the cluster receive the updated schema through database replication.

  1. Click . A window opens confirming the database schema upgrade.
  2. Click OK

The database schema upgrade starts. Once the database schema has been updated, the remaining nodes in the cluster install the updated schema through replication.