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

Changes in v1.9.3

Maintenance Release: August 31st, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5749
  • Controller:
    • Address an issue with unregistering HAProxy nodes (CLUS-1518)
    • Upgrade of the my.cnf template file for MariaDB Galera Cluster 10.6+

Maintenance Release: August 23rd, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5729
  • Controller:
    • Address an issue for MaxScale where static changes to /etc/maxscale.cnf had no effect new load_persisted_configs=false is now the default which makes changes to /etc/maxscale.cnf priority rather than dynamic changes which are saved to /var/lib/maxscale/maxscale.cnf.d (CLUS-1476).

Maintenance Release: August 17th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5719
    • clustercontrol2-0.7.0-516
  • Controller:
    • Address an issue where HAProxy admin user and password in the advanced settings were not properly set (CLUS-1409).
    • Address an issue with PostgreSQL primary failover failure. All cluster nodes are now granted in all pg_hba.conf files at cluster deployment. (CLUS-1459).
    • Address an issue to drop cmon_host_log table since it no longer is in use.
  • Frontend (UI):
    • Address an issue with MS SQL Server deployments to use the hostname returned from the SSH connection check (CCV2-475 Note: Additional improvements are in progress).
    • Address an issue to show a link to the T&C on the login page (CLUS-1464).

Maintenance Release: August 8th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5694
    • clustercontrol-notifications-1.9.3-322
    • clustercontrol2-0.7.0-509
  • Controller:
    • Address an issue where ProxySQL deployment fails on MariaDB 10.6 (CLUS-1460).
    • Address an issue where DB user/account creation fails on MariaDB 10.6 (CLUS-1431, CLUS-1449, CLUS-1456).
    • Address an issue to include Controller/CMON and cluster name for notifications (CLUS-1416).
  • Frontend (UI):
    • Address an issue with FQDN when deploying MS SQL Server 2019 (CCV2-473, CCV2-475).

Maintenance Release: July 29th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5668
    • clustercontrol-1.9.3-8395
  • Controller:
    • Address an issue with backward compatibility on MongoDB where the role detection using the isMaster command was removed for older versions (CLUS-1446)
    • Address an issue where the deployment job for HAProxy with PostgreSQL got stuck (CLUS-1450)
    • Address an issue with ProxySQL synchronization where using a user other than ‘proxysql-monitor’ failed to migrate to the new instance (CLUS-1367)
    • Address further improvements to support ProxySQL users with sha2 passwords (CLUS-1342)
  • Frontend (UI):
    • Address an issue adding MongoDB arbiter which failed because the incorrect type was used (regular router/mongos) (CLUS-1444)
    • Address an issue with the PgBouncer deploy/import page not showing up properly (CLUS-1437)

Maintenance Release: July 28th, 2022

  • Build:
    • clustercontrol-1.9.3-5661
  • Controller:
    • Address an issue to limit the number of audit log records returned to 100 if no boundary is specified (CLUS-1407)
    • Address an issue where the deployment job for HAProxy got stuck (CLUS-1450)

Maintenance Release: July 22nd, 2022

  • Build:
    • clustercontrol-1.9.3-5639
  • Controller:
    • Address an issue where a stopped cluster changed state to failure instead of stopped (CLUS-1425)
    • Address an issue where the ProxySQL synchronization job failed but showed up as successful (CLUS-1426)
    • Address an issue where deleting a ProxySQL user only deleted it from the backend and not the frontend (CLUS-1428)
    • Address an issue when updating the ProxySQL frontend user entry which did not update the backend entry (CLUS-1430)
    • Address an issue with minor upgrades with MariaDB where packages to upgrade failed to match (CLUS-1362)

Maintenance Release: July 18th, 2022

  • Build:
    • clustercontrol-1.9.3-8378
  • Controller:
    • Address an issue where audit log records retrieval was not restricted. It now uses pagination correctly. (CLUS-1407)

Maintenance Release: July 7th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5598
    • clustercontrol-1.9.3-8374
  • Controller:
    • Address an issue where the my.cnf file was modified after adding a MySQL (galera) node. The my.cnf is now considered immutable if the cluster has been imported (CLUS-1396)
    • Address an issue starting/stopping EOL version of PostgreSQL 9.6 (CLUS-1406)
  • Frontend (UI):
    • Address an issue to toggle off native ProxySQL clustering if import configuration is set and vice versa (CLUS-1368)

Maintenance Release: June 27th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5569
  • Controller:
    • Address an issue where the same parameter name (MySQL) with lower and upper case was saved twice (CLUS-1372)
    • Address an issue to upgrade CMON when the MySQL password used had special characters (CLUS-1365)

Maintenance Release: June 24th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5565
    • clustercontrol-1.9.3-8355
  • Controller:
    • Address an issue with rebuild/add replication node (MySQL 5.7) with parsing the binary log position (CLUS-1357)
    • Address an issue with rebuilding replication node (MySQL) due to the format of host: port (CLUS-1370)
    • Address an issue with ProxySQL clustering when synchronizing settings for new nodes (further improvements planned) CLUS-1340
  • Frontend (UI):
    • Address an issue with rebuild replication node (MySQL) where the primary node is not recognized to be part of the cluster. (CLUS-1360)

Maintenance Release: June 15th, 2022

  • Build:
    • clustercontrol-controller- 1.9.3-5544
    • clustercontrol-1.9.3-8345
  • Controller:
    • Address an issue with MySQL DB user management to handle SENSITIVE_VARIABLES_OBSERVER introduced with MySQL 8.0.29 (CLUS-1341)
    • Address further improvements to correctly handle backup retentions (CLUS-1331)
    • Address an issue where cluster de-registration cleanup is now taken care of in the backend/cmon (CLUS-1336)
  • Frontend (UI):
    • Address an issue where adding an external mail notification address failed. (CLUS-1339)
    • Address an issue to indicate whether a MySQL node is read-only or writable when rebuilding replication secondary (CLUS-1314)
    • Address an issue where cluster de-registration cleanup is now taken care of in the backend/cmon (CLUS-1336)

Maintenance Release: June 8th, 2022

  • Build:
    • clustercontrol-controller-1.9.3-5529
    • clustercontrol-1.9.3-8335
  • Controller:
    • Address an issue where rebooting a host is stuck. A hard timeout of 60s has been enabled. (CLUS-1322)
    • Address an issue with backup retention where backups were not purged in time (CLUS-1331)
    • Address an issue where backups and backup records were left after deleting a cluster (CLUS-1218)
    • Address an issue where CMON retries connecting to a MySQL node with insecure connection – Use new connect_heartbeat_when_faulty=30 (30s default) to block connection attempts until the correct certs are used/configured (CLUS-1278)
  • Frontend (UI):
    • Address an issue when deleting a cluster to choose whether backups should be removed/deleted as well or left intact (CLUS-1218)

Maintenance Release: May 31st, 2022

  • Build:
    • clustercontrol-controller-1.9.3-5500
  • Controller:
    • Address an issue where PgBackRest failed because the backup host’s port was not passed forward (CLUS-1323 | CLUS-1319)
    • Address an issue to customize the time before attempting a PostgreSQL failover. Increase the number of sampling rounds with replication_failover_wait_extra_sampling_rounds (default 0) (CLUS-523)
    • Address an issue where CMON segmentation faults during backup verification (CLUS-1321)

Maintenance Release: May 27th, 2022

  • Build:
    • clustercontrol-controller-1.9.3-5488
  • Controller:
    • Address an issue where rebuilding a replication secondary (slave) failed on Galera clusters (CLUS-1303)

Maintenance Release: May 24th, 2022

  • Build:
    • clustercontrol-controller-1.9.3-5475
    • clustercontrol-1.9.3-8324
  • Controller:
    • Address an issue, where MariaDB 10.5.16 and later changed xtrabackup_binlog_info. This caused a parsing error which could lead to rebuilding /staging of secondary replication nodes could fail (CLUS-1316)
    • Address an issue where importing MySQL/MariaDB systems could fail due to a parsing error of the IP/hostname address (CLUS-1315)
    • Address an issue in ProxySQL when syncing nodes could cause privileges to not be fully synced (CLUS-1289)
  • Frontend (UI):
    • Address an issue with license stats when counting the number of Galera nodes (CLUS-1317)

Maintenance Release: May 23rd, 2022

  • Build:
    • clustercontrol-controller-1.9.3-5466
  • Controller:
    • Address an issue with MariaDB where the wrong mysqld binary name was used (mysqld vs mariadbd) (CLUS-1312)
    • Address an issue where backup records were not added for some failed backup jobs (CLUS-1272)
    • Address an issue to use systemctl instead of pg_ctl to start/stop PostgreSQL (CLUS-1260)
    • Address an issue to customize the mail subject with a new parameter – email_subject_prefix (CLUS-1244)

Maintenance Release: May 19th, 2022

  • Build:
    • clustercontrol-1.9.3-8321
    • clustercontrol-ssh-1.9.3-125
  • Controller-ssh:
    • Address issues upgrading the clustercontrol-ssh package
  • Frontend (UI):
    • Address issues with informing and re-directing users to CCv2 with Elasticsearch, Redis, and SQL Server (CLUS-1301, CLUS-1304)

Maintenance Release: May 13th, 2022

  • Build:
    • clustercontrol-controller-1.9.3-5451
  • Controller:
    • Address an issue where pg_backrest created the directory /home/pgbackrest. It now uses /var/lib/pgbackrest instead (CLUS-1173)
    • Address an issue with warnings of a non-existing maxscale1.log file (CLUS-1246)
    • Address an issue with Microsoft SQL Server deployment due to the failure of creating a SA user (CCv2-281)

Initial Release: May 11th, 2022

  • Build:
    • clustercontrol-1.9.3-8303
    • clustercontrol-controller-1.9.3-5439
    • clustercontrol-cloud-1.9.3-350
    • clustercontrol-notifications-1.9.3-310
    • clustercontrol-ssh-1.9.3-122
    • clustercontrol2-0.6.0-425

With our second major release of ClusterControl in 2022, we are excited to introduce support for the community edition of Elasticsearch 7.x and 8.x. It’s one of the most popular open-source full-text search and analytics engines on the market today and provides near real-time search and analytics for any kind of data, whether structured or unstructured.

In this initial version, you can use Elasticsearch with single node deployment for development or use it for production in a clustered deployment complete with backup management and scaling.

ClusterControl v2 (new web frontend) is becoming more feature complete and we have added support for Elasticsearch, MySQL Galera, PostgreSQL, TimescaleDB, and MongoDB Replicaset.

We still have some ways to go, however more of the core features to manage our full range of supported database technologies are becoming available to use.

In ClusterControl v1’s web application there is now a dedicated audit log page to track user and system activities for increased security and compliance.

Features

Elasticsearch 7.x, 8.x

  • Full-text search and analytics engine.
    • Deploy one node for test or development environments
    • Deploy three or more nodes for clustered deployments with master or data roles
    • Basic User Authentication with username and password
    • TLS/SSL API endpoint encryption
    • Backup Management with local storage repository
    • Scaling out or in master or data nodes
  • Current limitations:
    • No cloud storage (object) repository
    • No dashboards/performance charts
    • Only Ubuntu 20.04 and RedHat/CentOS 8 are supported
    • Configuration files management and Upgrades are not supported at this time

Audit Logging

  • The new Audit Log page is accessible via the Activity → Audit Log (ClusterControl v1 web frontend) and Activity Center (ClusterControl v2 web frontend)
  • Activities tracked:
    • User authentication, cloud credentials, database configuration, and users changes
    • CMON configuration changes and jobs
    • CC user management changes (Users and ACLs), operational report
  • New CMON audit log configuration parameters
    • audit_logfile, default log filename (/var/log/cmon_audit.log)
    • audit_ignore_users, skip default users (system, ccrpc).

Miscellaneous

  • Streaming backups with xtrabackup can now be compressed with the addition of new CMON configuration parameters (no frontend at this time)
    • xtrabackup_compress_threads, xtrabackup_parallel, xtrabackup_manual_args
  • The cluster overview in ClusterControl v1 application is now using data from the Prometheus server (if available)
  • Delete local backup after cloud upload
  • New bootstrap option when starting Galera nodes

ClusterControl v2

  • Deploy/Import and manage MySQL Galera, PostgreSQL, TimescaleDB and MongoDB Replicaset clusters
    • Backup management, Cluster, and node actions
    • Dashboards/performance charts for database and load balancers
  • Deploy/Import and manage HAProxy with Keepalived
    • HAProxy status/performance node page
  • SSH host health-check to verify SSH connectivity
  • Multiple maintenance modes
  • Rebuild node for Microsoft SQL Server nodes

FAQs

Q: How can I start using Elasticsearch?

A: Please follow the instructions outlined in the Getting Started with ClusterControl v2 to install ClusterControl v2 and then use the Service Deployment wizard to deploy an Elasticsearch cluster.

Q: Can I separate the location of my Elasticsearch master and data nodes?

A: Yes, you can separate the master and data nodes to be on different hosts.

Q: What are the minimum requirements for a clustered Elasticsearch deployment?

A: Yes, you can separate the master and data nodes to be on different hosts.

You need:

  • At least three nodes in the master role
  • At least two nodes in the data role
  • At least two nodes of each role; master and data

Q: Can I rebuild an Elasticsearch node?

A: No there is no need, the Elasticsearch cluster automatically partitions the dataset across all available data nodes. You can remove and add a data node if you need to for example terminate and relaunch the VM the node runs on.

Q: Can I deploy other load balancers like ProxSQL with ClusterControl v2’s web application?

A: Not yet with this release, unfortunately. We are working on adding the remaining supported load balancers and connection pooling. Expect it to be available in an upcoming release of the ClusterControl v2’s user interface.

  • ProxySQL
  • MaxScale
  • Garbd
  • PgBouncer
Was this article helpful to you? Yes No