1. Home
  2. Docs
  3. ClusterControl
  4. Changelogs
  5. Changes in v1.9.7

Changes in v1.9.7

Maintenance Release: September 20th, 2023

  • Build:
    • clustercontrol-controller-1.9.7-6542
  • Controller:
    • Address an issue when doing a reconfigure ‘backup dir’ with PBM (CLUS-2526).
    • Address issue with pgBackRest and automatically rebuild replicas after restore. This is enabled by default now (CLUS-2711).
    • Address an issue with LDAP authentication failing when there is a DN change on the directory service side (CLUS-2633).
    • Address an issue where PBM fails after upgrading to 1.9.7 (CLUS-2640).

Maintenance Release: September 13th, 2023

  • Build:
    • clustercontrol-controller-1.9.7-6524
  • Controller:
    • Address an issue when restoring with pg_basebackup where the replicas were not automatically rebuilt. This is now the default behavior (CLUS-2711).
    • Address issues with PITR pg_basebackup. If no PTIR time is set then recovery_target is set to immediate (CLUS-2609).
    • Address an issue with not masking the password when pg_basebackup failed in the job log (CLUS-2638).
    • Address an issue with ProxySQL when adding a new user (CLUS-2616, CLUS-2678).

Maintenance Release: September 11th, 2023

  • Build:
    • clustercontrol-controller-1.9.7-6517
    • clustercontrol-1.9.7-8642
  • Controller:
    • Address an issue of failing to promote replicas when there is nothing to catch up on the primary (CLUS-2559).
    • Address an issue with the license at deployment time (CLUS-2478).
    • Address an issue disabling ‘read-only’ on a node when auto_manage_readonly=false (CLUS-2501).
    • Address an issue with creating a cluster from backup with MySQL Galera (CLUS-2594).
    • Address an issue with MariaDB Enterprise where -no-backup-locks is not supported (CLUS-2612).
    • Address an issue to raise alarms when CMON starts up with potentially invalid configuration files and silently fails (CLUS-2367).
  • Frontend (UI):
    • Address an issue where backup_failover_host=auto was incorrectly sent to CMON (CLUS-2592).

Maintenance Release: August 26th, 2023

  • Build:
    • clustercontrol-controller-1.9.7-6488
  • Controller:
    • Address an issue where the ‘vendor=postgres’ failed to be recognized after upgrading to 1.9.7 (CLUS-2601).

Initial Release: August 25th, 2023

  • Build:
    • clustercontrol-1.9.7-8636
    • clustercontrol-controller-1.9.7-6487
    • clustercontrol-cloud-1.9.7-395
    • clustercontrol-notifications-1.9.7-339
    • clustercontrol-ssh-1.9.7-151
    • clustercontrol2-2.0.0-979

In this release, we have added support for the following key features:

  • Enterprise Vendors for PostgreSQL and MongoDB – use enterprise software repositories.
  • Support for PostgreSQL 15, MongoDB 6.0, MariaDB 10.11, and MS SQL Server 2022.
  • Support for RedHat 9, AlmaLinux 9, and RockyLinux 9.
  • General Availability of our new web frontend – ClusterControl v2
    • Mail notifications, Certificate management
    • Advisors, Incident management services, Topology View


Enterprise Vendors

ClusterControl now supports using Enterprise vendors for PostgreSQL and MongoDB. You can manage and monitor EDB Postgres Advanced Server and MongoDB Enterprise clusters by using their enterprise repositories when provisioning databases. You need a valid repository token (depending on the vendor) in order to use the enterprise packages.

The s9s CLI adds two new vendor (–vendor) options:

  • enterprisedb for EDB Postgres Advanced Server
  • mongodbenterprise for MongoDB Enterprise

ClusterControl v2.0 – New web frontend

We have been migrating the feature set of the ClusterControl GUI (v1) to a new web frontend. This is a completely rewritten web application that aims to modernize the UI and improve the user experience and ease of use.
It is now in a state where we have feature parity with the old user interface. You can start using ClusterControl (GUI) v2 without having to rely on the functionality of the old web application.

‘CCv2’ is now the default web application when you install ClusterControl following the product download page instructions. The old web application ‘CCv1’ is still accessible until the end of the year at which time it will no longer be supported.

Upgrade to CCv2

You can upgrade/move from the CCv1 web application to the CCv2 web application with a few easy steps (existing ClusterControl installation). This setup will still provide access to the old ‘CCv1’ user interface while the new web application is accessible at another port.

Upgrade notes:

  • The 3rd party notifications configurations for PagerDuty, Opsgenine, Slack, etc. need to be manually re-created in CCv2 and removed from CCv1.
  • The DB Status and DB Variables pages are coming in a future CCv2 patch.


Steps described in the following sections should be performed on the ClusterControl node unless specified otherwise.

Red Hat/AlmaLinux/RockyLinuxDebian/Ubuntu
$ yum clean all
$ yum install clustercontrol2
$ systemctl restart httpd

Open the web browser and go to https://{ClusterControl_host}:9443. Log in with your user credentials used with ‘CCv1’

$ apt update
$ apt install clustercontrol2
$ systemctl restart apache2

Open the web browser and go to https://{ClusterControl_host}:9443. Log in with your user credentials used with ‘CCv1’

Was this article helpful to you? Yes No