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

Changes in v1.9.1

Maintenance Release: November 24th, 2021

  • Build:
    • clustercontrol-1.9.1-8170
    • clustercontrol-notifications-1.9.1-300
    • clustercontrol-cloud-1.9.1-328
  • Frontend (UI):
    • Fixed an issue with editing backup schedules where ‘exclude tables’ reverted to ‘include tables’ instead.
    • Address an issue where the node’s action menu did not appear on the nodes for the nodes page.
  • Cloud:
    • Fixed an issue with multi parts upload to cloud object storage (S3) where parts per upload have been increased to 1000.
  • Notifications:
    • Fixed an issue with the notifications configuration for ‘All Clusters’. It previously only considered clusters that were managed at the time when the configuration was created. It now correctly sends notifications for all managed clusters regardless of when a cluster was created/added.

Maintenance Release: November 15th, 2021

  • Build:
    • clustercontrol-1.9.1-8162
    • clustercontrol-controller-1.9.1-4940
  • Frontend (UI):
    • The new bootstrap.php variable DISABLE_PHPCAKE_DEBUG_LOG disables by default the debug.log file at /var/www/html/clustercontrol/app/tmp/logs.
    • ProxySQL: The UI now differentiates between a ProxySQL user (frontend) and MySQL user (backend).
    • Cluster list: Cluster-to-Cluster replication now correctly shows a bi-directional arrow between the clusters.
  • Controller:
    • MySQL: Create Slave Cluster can now use uni-directional instead of bi-directional replication.
    • MYSQL: Fix an issue where the PID of the MySQL server was missing on the nodes page with custom MySQL ports.
    • MySQL Galera: ‘Start node job’ message clarification that it can take a while for IST or SST to complete.
    • Backups: Improvements on how netcat/socat ports are allocated to prevent potential socket collisions with concurrent backup jobs.
    • LDAP: The cmon-ldap.cnf file can now also be read from /etc/cmon.d/cmpn-ldap.cnf which is now the new preferred location instead of /etc/cmon-ldap.cnf.
    • Documentation: Clarification for replication_auto_rebuild_slave which only applies to rebuilding slaves.

Maintenance Release: November 8th, 2021

  • Build:
    • clustercontrol-controller-1.9.1-4926
  • Controller:
    • LDAP: Brackets are now properly escaped.
    • Fix a license issue with HAProxy nodes.
    • Fix an issue in the topology view where not all MySQL nodes were shown.

Initial Release: November 3rd, 2021

  • Build:
    • clustercontrol-1.9.1-8151
    • clustercontrol-controller-1.9.1-4912
    • clustercontrol-cloud-1.9.1-322
    • clustercontrol-ssh-1.9.1-115
    • clustercontrol-notifications-1.9.1-297

With our third major release of ClusterControl in 2021, we are excited to announce support for Microsoft SQL Server 2019!

MS SQL Server 2019 has been one of our most customer-requested databases and is also one of the most recommended and popular enterprise-grade databases with over 30 years on the market.

Our first supported closed source database, its initial release includes automated deployments, node recovery, and backup management.

In addition, we also now support MongoDB with the most recent GA versions v4.4 and v5.0.

Let us know what you think about these features and changes anytime.

 

Feature Details

  • Microsoft SQL Server 2019
    • Currently, MS SQL Server 2019 can be deployed as a standalone/single server. We support “full”, “differential” and “transaction log” backups – The backups can only be stored on the database node.
    • Current limitations:
      • Only Ubuntu 20.04 and RedHat/Centos 8 are supported.
      • Only MS SQL Server 2019 is supported.
      • Configuration files management, Scaling, and Upgrades are not supported.
      • Backups cannot be stored on the Controller (CMON) host.
      • SSL/TLS is not supported.
    • Planned features:
      • Always On availability groups.
      • Performance monitoring (in the CCv2 frontend).
      • Cloud upload for backups.
      • Backup verification.
  • MongoDB
    • We have added support for these new GA versions of MongoDB.
    • Percona Server for MongoDB v4.4 and v5.0
    • MongoDB Inc v4.4 and v5.0
  • ClusterControl v2
    • Import Redis with Sentinel cluster is now supported.
    • New cluster actions
      • Enable/disable maintenance mode
      • Enable/disable read-only (MySQL)
      • Restart cluster (Galera)
      • Remove cluster
    • New node actions for MySQL
      • Enable/disable maintenance mode
      • Enable/disable read-only
      • Enable/disable binary logging (Galera)
      • Promote replica
      • Stop replica
      • Reset replica
      • Rebuild replica
      • Change replication primary
      • Reboot host
      • Restart node
      • Stop node
      • Remove node
  • Misc
    • Split-brain improvements with MySQL Replication (Primary/Replicas). The nodes will be set to ‘read only’ if we cannot reliably detect a new primary.
    • PgBackRest backups can now enable encryption from the web application (previously only available with the s9s command-line client).
  • FAQ
    • How can I start using MS SQL Server 2019 or Redis with ClusterControl
      • We are transitioning to a new version of our ClusterControl web frontend/application and these new databases are currently only available by using our technical preview of ClusterControl v2. 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 or import your Redis or MS SQL Server 2019 database.
    • What are the OS requirements for deploying MS SQL Server 2019?
      • Deploy MS SQL Server 2019 on Ubuntu 20.04 or RedHat/Centos 8.
    • What are the OS requirements for deploying Redis?
      • Deploy Redis v5 & v6 on Ubuntu 20.04 or RedHat/Centos 8.
    • What are the features and limitations of Redis?
      • Redis databases are deployed with Sentinel nodes that are co-located on the same host. You can deploy 1, 3, or 5 nodes. Backups are created for:
        • RDB (database). The RDB persistence performs point-in-time snapshots of your dataset at specified intervals.
        • AOF (Append Only File). The AOF persistence logs every write operation received by the server, that will be played again at server startup, reconstructing the original dataset.
      • Current limitations and planned features:
        • Performance monitoring (in the CCv2 frontend) will be supported in an upcoming release.
        • No cloud upload for backups — will be supported in an upcoming release.
        • Configuration files management, Scaling, and Upgrades are not supported.
        • No backup verification.
        • SSL/TLS is not supported.
Was this article helpful to you? Yes No