hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Cleaned up Limitations

Browse Source
This commit is contained in:
Markus Makela 2015-09-29 10:23:04 +03:00
parent fcb13760fb
commit 6f3ec723b1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/About/Limitations.md
View File

@ -10,8 +10,6 @@ This section describes the limitations that are common to all configuration of p
Compression is not included in MySQL server handshake
## Limitations with MySQL Master/Slave Replication monitoring
## Limitations with Galera Cluster Monitoring
Master selection is based only on MIN(wsrep_local_index), no other server parameter.
@ -35,7 +33,9 @@ In master-slave replication cluster also read-only queries are routed to master
* statement includes a stored procedure, or an UDF call
### Limitations in client session handling
Some of the queries that client sends are routed to all backends instead of sending them just to one of server. These queries include `USE <db name>` and `SET autocommit=0` among many others. Readwritesplit sends a copy of these queries to each backend server and forwards the master's reply to the client. Below is a list of MySQL commands which are classified as session commands :
```
COM_INIT_DB (USE <db name> creates this)
@ -90,4 +90,4 @@ Most imaginable reasons are related to replication lag but it could be possible
## Authentication Related Limitations
MySQL old passwords are not supported
MySQL old style passwords are not supported. MySQL versions 4.1 and newer use a new authentication protocol which does not support pre-4.1 style passwords.