Skip to content
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.

Latest commit

 

History

History
13 lines (8 loc) · 1.76 KB

known-issues.md

File metadata and controls

13 lines (8 loc) · 1.76 KB

verify-cluster-schemas issue in cf-mysql v36

In v36, we introduced a way to limit admin access to the database by adding the cf_mysql.mysql.remote_admin_access property. When set to false, no user is able to connect to the database as the admin user from a remote host. The verify-cluster-schemas errand is not compatible with this restriction, and cannot run when cf-mysql is deployed in this configuration.

Build issue with cf-mysql v26

The release tagged v26 will no longer build from source due to a dependency that is no longer available. To continue working from source, update your source tree to develop.

MyISAM Tables

The clustering plugin used in this release (Galera) does not support replication of MyISAM Tables. However, the service does not prevent the creation of MyISAM tables. When MyISAM tables are created, the tables will be created on every node (DDL statements are replicated), but data written to a node won't be replicated. If the persistent disk is lost on the node data is written to (for MyISAM tables only), data will be lost. To change a table from MyISAM to InnoDB, please follow this guide.

Max User Connections

When updating the max_user_connections property for an existing plan, the connections currently open will not be affected (ie if you have decreased from 20 to 40, users with 40 open connections will keep them open). To force the changes upon users with open connections, an operator can restart the proxy job as this will cause the connections to reconnect and stay within the limit. Otherwise, if any connection above the limit is reset it won't be able to reconnect, so the number of connections will eventually converge on the new limit.