[MXS-2991] Enable MaxScale SchemaRouter for 'simple' SchemaRouting. Created: 2020-05-12  Updated: 2020-10-19  Resolved: 2020-10-19

Status: Closed
Project: MariaDB MaxScale
Component/s: schemarouter
Affects Version/s: 2.4.9
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Oophoo6s Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: Compatibility, need_feedback
Environment:

MaxScale 2.4.9 on Debian 10.3
MariaDB 10.1 on Debian 8.11
MariaDB 10.4 on Debian 10.3


 Description   

I had problems using MaxScale SchemaRouter in conjunction with applications like Matomo (Piwik), phpMyAdmin and Directus. The setup consisted of two MariaDB servers with the application databases residing on either one of the servers.

In case of Matomo there were errors like 'SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected - in plugin Actions' in the logs. The Matomo docs state the following 'MySQL' requirements: 'Matomo won't work with a MySQL load balancer such as ProxySQL unless you can ensure that all queries within a given established connection are always sent to the same database server'.

I guess the reason for the other applications to fail has a similar cause. It seems that MaxScale isn't able to properly route the queries to the right server in such a setup ?because it tries to do ShardRouting instead of SchemaRouting (just a hunch)?

 Comments   
Comment by markus makela [ 2020-05-13 ]

Can you post some of the queries that cause those errors to be generated? You can enable the verbose logging in MaxScale by adding log_info=true under the [maxscale] section.

Comment by Oophoo6s [ 2020-05-14 ]

I can't reproduce the problem at the moment. I ran into the problem a few weeks ago and the MariaDB server parameters have changed ever since because of other compatibility issues (the MaxScale instance/VM is still in place but not in use). At the time the servers ran different SQL MODES - the defaults for their respective versions (10.1 and 10.4). Now both servers run the SQL_MODE as of 10.1 and innodb_strict_mode disabled. It's kind of complicated to recreate the same conditions now. I'll give it a shot but it might take a few days.

Comment by markus makela [ 2020-07-03 ]

I think this might be solved by either the latest fixes in the 2.4 branch or by (you're already using a new enough version) the new features in the upcoming 2.5 release of MaxScale (you can test the beta version of it that's currently available on the mariadb.com site).

Comment by markus makela [ 2020-08-27 ]

Oophoo6s please test this with the latest 2.5 version of MaxScale.

Comment by markus makela [ 2020-10-19 ]

I'll close this as there's been no progress and we haven't been able to reproduce this. If this still fails with the latest 2.5 release, please let us know and we'll reopen this issue.

Generated at Thu Feb 08 04:18:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.