Maintenance Release: May 18th, 2018
- PostgreSQL: Support for init scripts for RHSCL PosrgreSQL packages. Please note that further tuning of the environment may be needed.
- PostgreSQL: Improved logic to locate the Postgres log files.
- PostgreSQL: Verifying the configuration and
listen_addressesbefore registering the node.
- PostgreSQL: Better error reporting in case of connection timeouts.
- PostgreSQL: Improvements and better messaging of slave recovery in case of the host being down.
- MySQL/Galera: Properly handle quoted
- Backup: Running a backup prevented other jobs from being executed.
- Backup: A fix to prevent a backup to be uploaded to the cloud when the user did not ask for it.
- Error reporting: A fix for Access denied when S9s CLI created a user.
- General: Removed the printout
RPC: No variables available for....
Maintenance Release: May 17th, 2018
- Fix to add missing admin port option for ProxySQL installations and registrations.
- Fix replication lag not shown properly for MySQL Replication clusters.
- Fix to allow changing the default region with a cloud credential.
- Fix to restart a failed PostgreSQL job.
Maintenance Release: May 7th, 2018
- Fix an issue with the security group on AWS preventing cloud deployment to work if ClusterControl was installed in the same VPC.
- Bump version of clustercontrol-notifications to 1.6.0.
Maintenance Release: May 4th, 2018
- Security Vulnerability: Fixed an issue where it was possible to perform an XSS attack.
- Cloud Deployments: Fixed a missing validation of the SSH Key.
- LDAP: Add support to get the user group from a
Maintenance Release: May 2nd, 2018
- LDAP: Fix an issue preventing users to login with anything else than an email address.
- Changed default
/usrfor MySQL Cluster (NDB) import.
- Fix for an issue where a failed ProxySQL node was added and then not removable.
- Fix for an issue with a blank page with DB User Management when default anonymous users (test users) are detected.
- Add validation when trying to use reserved words with PostgreSQL deployments.
- Tune the custom advisor dialog for lower resolution screens.
- Fix a regression preventing error reports from being created from the frontend.
- NDB Cluster: SELinux settings were not checked correctly.
- NDB Cluster: The Install Software option was not respected.
- NDB Cluster: Fixed an issue detecting disk space and calculating the size of the REDO log.
- Postgres: Add Replication Slave will fail if there is an existing Postgres server running on the node, and also check if the psql client is available.
- PostgreSQL: Forbid using reserved SQL keywords as PostgreSQL username (as it is an identifier there which can not be a reserved keyword).
- Backup (xtrabackup): Fixed an issue where an Incremental backup could be created without having a Full backup. Now the following will happen: If there is no Full backup, the Incremental backup will be executed as a Full backup.
- MaxScale: Version 2.2.x support.
Initial Release: April 17th, 2018
Welcome to our new 1.6.0 release! Restoring your database using only a backup for disaster recovery is at times not enough. You often want to restore to a specific point in time or transaction after the backup happened. You can now do Point In Time Recovery – PITR for MySQL based databases by passing in a stop time or an event position in the binary logs as a recovery target.
We are also continuing to add cloud functionality:
- Launch cloud instances and deploy a database cluster on AWS, Google Cloud, and Azure from your on-premise installation.
- Upload/download backups to Azure cloud storage.
- Our cluster topology view now supports PostgreSQL replication clusters and MongoDB ReplicSets and Shards. Easily see how your database nodes are related to each other and perform actions with intuitive drag and drop motion.
As in every release we continuously work on improving our UX/UI experience for our users. This time around we have re-designed the DB User Management page for MySQL based clusters. It should be easier to understand and manage your database users with this new user interface.
- Point In Time Recovery – PITR (MySQL)
- Position and time-based recovery for MySQL based clusters.
- Recover until the date and time given by Restore Time (Event time – stop date&time).
- Recover until the stop position is found in the specified binary log file. If you enter
binlog.001827it will scan existing binary logs files until
binlog.001827 (inclusive) and not go any further.
- Deploy and manage clusters on public Clouds (BETA)
- Supported cloud providers
- Amazon Web Services (VPC).
- Google Cloud.
- Microsoft Azure.
- Supported databases:
- MySQL Galera.
- MongoDB ReplicaSet.
- Current limitations:
- There is currently no accounting in place for cloud instances. You will need to manually remove created cloud instances.
- You cannot add or remove a node automatically with cloud instances.
- You cannot deploy a load balancer automatically with a cloud instance.
- Supported cloud providers
- Topology View
- Support added for:
- PostgreSQL Replication clusters.
- MongoDB ReplicaSets and Sharded clusters.
- Support added for:
- Improved cluster deployment speed by utilizing parallel jobs. Deploy more than one cluster in parallel.
- Re-designed DB User Management for MySQL based clusters.
- Support to deploy and manage MongoDB cluster on v3.6.