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

Changes in v1.9.0

Maintenance Release: September 30th, 2021

  • Build:
    • clustercontrol-1.9.0-8122
    • clustercontrol-controller-1.9.0-4846
  • Controller:
    • Enable changing passwords on the Settings → Runtime Configuration page without having to restart the ClusterControl controller (CMON).
    • Fixed an issue ordering the cluster list by name when using cluster-to-cluster replication.
    • Fixed an issue where the failover backup host dropdown was empty with “auto” as the backup host.
    • Fixed for the blank confirmation dialog when setting a maintenance mode.
    • MySQL: Fix an issue with Add Replication Slave when the database admin user username is not root.
    • Fixed an issue with warning/critical alarms for disk-space usage. Only warnings with a hardcoded threshold were sent out.
    • Increased a timeout to fix the issue where the PBM (Percona Backup for MongoDB) agent failed to start (pid is 0).
    • Cloud Deployment: Ubuntu 20.04 is no longer shown when selecting MongoDB v4.0 or v4.2.

Maintenance Release: September 22nd, 2021

  • Build:
    • clustercontrol-controller-1.9.0-4814
  • Controller:
    • Redis: Fix an issue using a custom dbfilename and/or appendfilename in the redis.conf.

Maintenance Release: September 13th, 2021

  • Build:
    • clustercontrol-1.9.0-8079
    • clustercontrol-controller-1.9.0-4801
  • Frontend (UI):
    • PgBackRest now has an option in the frontend to enable encryption.
  •  Controller:
    • The Prometheus server version that is installed is now set to use v2.29.2.
    • MongoDB: A potential fix for an issue where the PBM (Percona Backup for MongoDB) agent failed to start (pid is 0).
    • MongoDB: Fixed an issue where the PBM (Percona Backup for MongoDB) agent was stuck when restoring with waiting for PITR to be disabled – (correctly detects pitr.enabled=true).
    • PostgreSQL: Fixed an issue with PgBackRest and using a dedicated repository host where the host port was misconfigured.
    • Fixed an issue with disk space alarms not clearly showing which filesystem is out of space.
    • A potential fix for an issue with Cluster-to-Cluster replication where doing inserts/updates fail.

Maintenance Release: September 6th, 2021

  • Build:
    • clustercontrol-1.9.0-8067
  • Frontend (UI):
    • MySQL replicas can now be forced to be promoted as a primary.
    • PgBackRest nodes are now shown in their own section on the Nodes page.
    • Importing Galera Cluster now allows replicas to use a different user than the root user.
    • Fixed a regression with sorting the cluster list based on the name.
    • Fixed an issue adding a MySQL replica node due to failing SSH check to the host.
    • Fixed for a presentation issue when having more than one Cluster-to-Cluster replication.

Maintenance Release: August 30th, 2021

  • Build:
    • clustercontrol-controller-1.9.0-4769
  • Controller:
    • A crashing issue has been resolved to cause CMON to segfault.
    • MySQL Replication: Fixed an issue adding replication slave with a PITR mysqldump backup.
    • PostgreSQL: Fixed an issue where streaming pg_basebackup could run forever if there was a socat running on the storage host.
    • Query Monitor V2: Fixed an issue when deploying Query Monitor v2 where the agent service was not enabled after installation, thus the agent would not restart automatically after a reboot.

Maintenance Release: August 20th, 2021

  • Build:
    • clustercontrol-controller-1.9.0-4756
    • clustercontrol-1.9.0-8051
    • clustercontrol-cloud-1.9.0-310
  • Controller:
    • MySQL: Fix to handle custom directory paths in a configuration at deployment or during an add node (using --copy-back or --move-back).
    • PostgreSQL: Backup verification server was not properly removed when the option was set.
    • Timescale: Fix for deploying TimescaleDB v12.
  • Cloud:
    • Backup: Fix an issue where uploading a backup to Azure stopped at 200GB.
  • Frontend (UI):
    • HAProxy: Fix an issue with server addresses showing up incorrectly.
    • Fix an issue with the Cluster Action menu disappearing when the activity viewer was open.

Deploying ProxySQL v1 is no longer supported. ProxySQL v2 is the only option as of this patch onwards.

Maintenance Release: August 15th, 2021

  • Build:
    • clustercontrol-controller-1.9.0-4747
    • clustercontrol-1.9.0-8040
  • Controller:
    • Fixed a bug where Adding HAProxy Load Balancer in a Cluster-to-Cluster replication (slave cluster) failed.
    • Fixed a bug installing HAProxy on Ubuntu 20.04 due to Unable to locate package haproxy18.
    • Failed to add replication slave for Galera cluster due to an error loading the wrong configuration template.
    • Fixed a bug where cluster failure is reported as “Warning”, but must be “Critical”.
    • Fixed an issue where failing to upload a backup to the cloud, e.g Azure did not raise any alarm and added more error messages in case of failure.
    • Fixed an SQL injection issue when configuring the ‘mail server’ settings.
    • Fixed an issue where backup verification failed because only a hostname was sent in the request and the port was missing.
    • Fixed an issue, when desyncing a Galera node during a backup would always return that the backup failed.
    • Added a feature making semi-sync replication (MySQL/MariaDB replication ) optional. A replica can however only have semi-sync enabled if the master already is configured with semi-sync.
  • Frontend (UI):
    • Fixed a but where it was impossible to create a schedule for xtrabackup or mariabackup.
    • Added a feature to make it possible to configurable retention by size for Prometheus.

Maintenance Release: August 10th, 2021

  • Build:
    •  clustercontrol-1.9.0-8025
  • Frontend (UI):
    • Create Secondary Cluster: Fixed an issue where the selected Master was not set in the job, thus the selected master host was never used.
    • Registration: Fixed a user registration issue.
    • Fixed a bug on the Email Notification page where it was possible to get Internal Server Error if an older PHP version is used (PHP < 5.5).
    • Improved Node Action dialogs and fixed typos.

Maintenance Release: August 9th, 2021

  • Build:
    • clustercontrol-controller-1.9.0-4730
  • Controller:
    • LDAP: Fixed a bug preventing LDAP login to work.
    • MySQL: Fixed an issue where RESET PRIMARY was used instead of RESET MASTER.
    • Galera: Fixed an issue restoring backups on more than one node and the datadir was not empty.
    • MySQL: The node action Reset Slave [All] now implicitly stops the replica threads. Before this, a user must first stop the slave before the RESET SLAVE command could be issued.
    • Upgrade: Fixed an issue where selecting one node would upgrade all nodes.
    • Webhook and Email Notifications: Fixed an issue when only “Ended” events were handled and not when the event was “Created”.

Maintenance Release: July 30th, 2021

  • Build:
    • clustercontrol-1.9.0-8008
  • Frontend (UI):
    • MySQL: Select async or semi-synchronous replication when deploying a replication cluster or adding a replica.
    • MySQL: Set a custom configuration template and datadir when adding a replica.
    • Topology View: Fix to allow more than 30 characters with node names.
    • Backup: Set a limit to the number of cores used when compressing with PIGZ.
    • Email notification: Fix for an issue where not all ClusterControl users are showing up properly in the list.

Initial Release: July 16th, 2021

  • Build:
    • clustercontrol-1.9.0-7991
    • clustercontrol-controller-1.9.0-4693
    • clustercontrol-cloud-1.9.0-307
    • clustercontrol-clud-1.9.0-307
    • clustercontrol-notifications-1.9.0-277
    • clustercontrol-ssh-1.9.0-109
    • clustercontrol2-0.1.0-165

Welcome to our second major release of 2021! We are excited to introduce support for Redis with Sentinel which provides high availability for your Redis nodes. Use a technology preview of our next-generation web frontend/application for ClusterControl to deploy, import and perform backup management for Redis with Sentinel nodes.

We also have a new Query Monitor system using an agent-based approach for MySQL and PostgreSQL-based databases. Using query monitor agents we are able to provide better accuracy and insights into your database performance with less load on the nodes. Analyze your database workloads by checking query digests, top queries or outliers.

In addition, we have worked on several improvements with pgBackRest for backing up PostgreSQL and you can also upload your backups to any cloud storage provider that supports AWS’s S3 object storage API.

Feature Details

  • Redis Management and Monitoring – An open-source in-memory data structure store that can be used as a database, cache or message broker, see redis.io for more information.
    Please see ClusterControl Tech Preview for instructions on how to install the technology preview to try out Redis Management and Monitoring.

    • Deploy Redis v5 or v6 nodes with Sentinels – one primary and up to five replicas.
    • Backup and restore with AOF and RDB.
    • Fault detection and failover orchestration by the Sentinels.
    • Stats collection and monitoring dashboard with Prometheus (coming soon).
  • Query Monitor – A new agent-based Query Monitoring system for MySQL and PostgreSQL.
    • Install and remove query monitor agents on the database nodes.
    • Start and stop collecting query stats with the agents.
    • New ‘Query Workload’ overview showing query digests, latency, throughput and concurrency with a scatter chart.
  • PostgreSQL
    • pgBackRest improvements
      • Install pgBackRest on primary or replica/standby nodes with a default stanza.
      • Install pgBackRest at cluster deployment.
      • Register/import existing pgBackRest nodes, unregister (keep config files) and uninstall pgBackRest (completely remove it).
      • Backup repository configurations – local (on one of the database hosts) or dedicated backup host.
      • Backup on replica/standby nodes.
      • Backup reconfiguration – regenerate configuration.
      • Support for stanza configured retention – set type to ‘time’ to match ClusterControl’s retention value in days.
      • Methods supported – pgbackrestfull, pgbackrestdiff, pgbackrestinc
      • Restore backup on primary – replicas need to be rebuilt separately.
      • Restore with custom tablespaces locations.
    • Backup verification
      • Point In Time Recovery with --pitr-stop-time.
  • Misc:
    • Upload backups to any AWS S3 API compliant cloud storage provider.
Was this article helpful to you? Yes 2 No