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

Changes in v1.7.3

Maintenance Release: October 21st, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3496
  • Controller:
    • HAProxy: Added tcp-check connect to configuration templates.

Maintenance Release: October 20th, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3494
    • clustercontrol-1.7.3-6429
  • Frontend (UI):
    • PostgreSQL: Fixed an issue with the charts on the Cluster Overview page.
  • Controller:
    • PostgreSQL: Query Monitor → Query Statistics, Exclusive Lock Waits was not working correctly and did not display all data.
    • Dashboard/SCUMM: Fixed an issue recovering Prometheus exporters in case of co-located cluster nodes by multiple-clusters.
    • MongoDB: Importing a single node will now fail if the node is not set up as a replica set member. Thus, it is the user’s responsibility to convert the node to a member before importing it.

Maintenance Release: October 13th, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3482
    • clustercontrol-1.7.3-6403
  • Frontend (UI):
    • Dashboards/PostgreSQL: Fixed an issue with Idle and Active Connections.
    • Backup: Can’t use backup verification server due to a bug in Host discovery.
    • Email Notifications: Improvements to email validation of External users and Adding/Removing of these External users.
  • Controller:
    • Dashboards/PostgreSQL: Active and Idle connection dashboards aren’t working for PostgreSQL. A redeploy of the postgres_exporter is needed.
    • Dashboards/PostgreSQL: Reverted back to postgres_exporter 0.4 as 0.5 was buggy.
    • Node Charts: Node CPU chart was incorrect on Centos6/RHEL6 because it had one less column (no guest-low counter value).
    • Notification: Fix daily limit handling of e-mail message recipients where -1 was not handled correctly.
    • Error-reporting: There was a problem with file listing when multiple files were specified since we bash-escape the paths for safety.
    • HAProxy: Fixed an issue parsing the HAProxy config file.
    • HAProxy: While setting up haproxy for PostgreSQL reading old password from the checker script fails.
    • PostgreSQL: Importing a node/cluster: If logging_collector=OFF and the user has not specified a custom log file then the job will be aborted and the user must specify it.

Maintenance Release: September 29th, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3450
    • clustercontrol-1.7.3-6368
  • Frontend (UI):
    • MySQL: Performance → Transaction Log uses timestamp and not epoch.
    • Fixes usability issues with Runtime Configuration making it easier to read
    • PostgreSQL: Fixes in Import/Add Replication Slave dialogs with respect to Port and Logfile fields.
  • Controller:
    • MySQL: Performance → Transaction Log uses timestamp and not epoch.
    • MySQL: Fixed an issue with excessive logging of long-running queries.
    • HAProxy: Fix of parsing errors during collect_configs cronjob (in case of HAProxy and ProxySQL nodes).
    • error-reporter: Include complete cmon log files and not only the last rows.

Maintenance Release: September 24th, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3440
  • Controller:
    • MySQL based systems: Fixed an issue with excessive logging of long-running queries.
    • SSH Communication: A number of improvements that fixes intermittent errors like test sudo failed and SUDO failed.

 Maintenance Release: September 17th, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3428
  • Controller:
    • MySQL Replication: A fix to update the status of the failed server in ProxySQL. The old master will now be marked as OFFLINE_SOFT. Any node that is not part of the replication topology is marked as OFFLINE_SOFT.
    • Added a fix that could cause a crash if a database connection could not be established.

Maintenance Release: September 10th, 2019

Maintenance Release: September 8th, 2019

  • Build:
    • clustercontrol-1.7.3-6340
    • clustercontrol-controller-1.7.3-3407
  • Frontend (UI):
    • Backup: Fixed an issue with scheduling a backup. If using cron settings, then due to TZs and conversions to UTC then a specified hour could be converted to an hour belonging to another day.
    • LDAP: Wrong LDAP status was shown in the UI
    • Email Notifications: Adding a recipient without having any clusters installed failed
  • Controller:
    • ProxySQL: Inserting a query rule with a duplicate query rule id caused the query rule ids smaller than the duplicate to become negative.
    • Prometheus version bump to v2.12
    • PostgreSQL: On RedHat systems, the default datadir was set to main instead of data.
    • MongoDB: Retention fails because all mongo backups were recognized as partial, and partial can only be removed if there are more than one full backups.
    • A fix for an infinite amount of ‘Job query is working again.’ log messages in the cmon log.
    • Removing storage of log messages in a deprecated table called collected_logs.

Maintenance Release: August 24th, 2019

  • Build:
    • clustercontrol-1.7.3-6322
    • clustercontrol-controller-1.7.3-3388
  • Frontend (UI):
    • PostgreSQL: Add Slave: help text next to logfile text box.
  • Controller:
    • Import/Add Cluster: Specified sudo password was not respected.
    • MongoDB: Importing a cluster failed even if the CAFile is specified following an error where it was not specified, because existing cert data was not updated in cmon’s certificate storage.
    • Controller: Must keep trying to connect to the MySQL server even if the MySQL server is not started, instead giving up and exit.
    • PostgreSQL: Whitelist is not working as documented.
    • SCUMM/Prometheus: General small improvements with disk device detection and mapping.

Maintenance Release: August 17th, 2019

  • Build:
    • clustercontrol-controller-1.7.3-3374
  • Controller:
    • PostgreSQL: a crashing bug was fixed that was caused by assuming that cluster_name always has a value.
    • PostgreSQL/pgbackrest: Fixed an issue when the backup.manifest is encrypted the backup appeared as failed. Please note that the backup. manifest record is not decrypted so some metadata information may not be updated (pending feature request).
    • Controller backup/save controller: Fixed an issue saving the controller with a non-quoted password causing mysqldump to fail.
    • ProxySQL: Fixed an issue where an error message was repeated due to trying to connect from a remote node using the admin user, which is forbidden in ProxySQL.
    • Error Reporting: Fixed a user handling issue, causing the error report to fail.
    • MySQL: Database Growth, adding more verbose logging in case of issue.

Maintenance Release: August 15th, 2019

  • Build:
    • clustercontrol-1.7.3-6298
    • clustercontrol-controller-1.7.3-3370
  • Controller
    • Performance → Transaction Log: Fixed an issue with pagination.
  • Frontend
    • Performance → Transaction Log: Fixed an issue with pagination.
    • Fixed an issue with JS code generation for older browsers by upgrading corejs.

Maintenance Release: July 29th, 2019

  • Build:
    • clustercontrol-1.7.3-6279
    • clustercontrol-controller-1.7.3-3336
  • Controller:
    • Added support for openntpd as an alternative to the ntp dependency.
    • MySQL 8.0: Fixed an issue where the keyword ‘groups’ was used in a query.
    • Improved error reporting in case of SSH errors when trying to determine the MySQL connection string.
    • PostgreSQL: Create a symlink to custom log file during add existing cluster as well, not only during add an existing node.
    • PostgreSQL: When adding an existing cluster, a custom specified log file will be used if logging_collector is off.
    • PostgreSQL: Fixed an issue detecting log files.
    • MySQL: A password could be visible in the ps output of a node when the cmon database was updated at controller startup.
    • Create/register cluster: Handle company_id if provided, otherwise, we try to query it up  user_id as a fallback.
  • Frontend (UI):
    • Fixed an issue where a cluster could not be registered due to a missing company id/team id.

Maintenance Release: July 24th, 2019

  • Build:
    • clustercontrol-1.7.3-6270
  • Frontend (UI):
    • Fix an issue saving and pushing out edited configuration files (Configuration Management).
    • Fix an issue with the Overview page not being properly shown after switching between tabs (PostgreSQL).

 Maintenance Release: July 18th, 2019

  • Build:
    • clustercontrol-1.7.3-6255
    • clustercontrol-controller-1.7.3-3319
  • Controller:
    • PostgreSQL: Fixes in log file handling to check if the log collector is enabled already. This could result in e.g the wrong log file was used.
    • PostgreSQL: A fix in multi-node support when adding nodes that could lead to nodes not being part of the replication topology.
    • PostgreSQL: Fixed an issue when the logfile was not owned by the postgres user.
    • PostgreSQL: Updated the repository signature.
    • TimeScaleDB: Fixed an issue adding a replication slave due to a version mismatch.
    • TimeScaleDB: Fixed an issue when rebooting TimeScaleDB and PostgreSQL master results in two master nodes.
    • MariaDB/Replication: Fixed an issue with Promote Slave (switch-over).
    • MariaDB/Galera: Fixed a check for the wsrep_sst_method to check whether xtrabackup vs. mariabackup is used.
    • MySQL/MariaDB: Importing a cluster could fail as it assumed bind_address existed as a server system variable.
  • Frontend (UI):
    • Add a workaround to sort the cluster list by name, status, type with a new bootstrap.php variable (instead of using cluster_id by the default):
        • define(‘CLUSTER_LIST_SORT_BY', 'name'); # sort by cluster name
    • Add additional information on how to use the ‘Stanza Name’ with PgBackRest backups
    • Add missing confirmation dialog for MongoDB restore a backup

Maintenance Release: July 16th, 2019

  • Build:
    • clustercontrol-1.7.3-6242
  • Frontend (UI):
    • Fix an HTML formatting issue when trying to change non-dynamic parameters in Configuration Management (MySQL).
    • Fix an issue with the Nodes → DB Performance chart which requested unfiltered datasets.

Maintenance Release: July 12th, 2019

  • Build:
    • clustercontrol-1.7.3-6226
  • Frontend (UI):
    • Fix missing mysqldump backups (PITR) for ‘Add Replication Slave’ when rebuilding with a backup.
    • Fix incompatible array notation with PHP v5.3.

Initial Release: July 2nd, 2019

  • Build:
    • clustercontrol-1.7.3-6209
    • clustercontrol-controller-1.7.3-3293
    • clustercontrol-cloud-1.7.3-217
    • clustercontrol-ssh-1.7.3-79
    • clustercontrol-notifications-1.7.3-182

In this release, we have added support for running multiple PostgreSQL instances on the same server with improvements to PgBackRest to support those environments. We have also added additional cluster types to our cloud deployment and support for scaling out cloud-deployed clusters with automated instance creation. Deploy MySQL Replication, PostgreSQL, and TimeScaleDB clusters on AWS, GCE, and Azure.

Feature Details

  • PostgreSQL
    • Manage multiple PostgreSQL instances on the same host.
    • Improvements to pgBackRest with non-standard instance ports and custom stanzas.
    • New Configuration Management page to manage your database configuration files.
    • Added metrics to monitor Logical Replication clusters.
  • Cloud Integration
    • Automatically launch a cloud instance and scale out your database cluster by adding a new DB node (Galera) or replication slave (Replication).
    • Deploy the following new replication database clusters:
      • Oracle MySQL Server 8.0
      • Percona Server 8.0
      • MariaDB Server 10.3
      • PostgreSQL 11.0 (Streaming Replication).
      • TimescaleDB 11.0 (Streaming Replication).
  • Misc
    • Backup verification jobs with xtrabackup can use the --use-memory the parameter to limit the memory usage.
    • A running backup verification server will show up in the Topology view as well.
    • MongoDB sharded clusters can add/register an existing MongoDB configuration node.The clustercontrol-cmonapi (CMON API) package is deprecated from now on and no longer required.
    • A few more legacy ExtJS pages have been migrated to AngularJS:
      • Configuration Management for MySQL, MongoDB, and MySQL NDB Cluster.
      • Email Notifications Settings.
      • Performance -> Transaction Logs.
Was this article helpful to you? Yes No