Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2991

Enable MaxScale SchemaRouter for 'simple' SchemaRouting.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.4.9
    • Fix Version/s: N/A
    • Component/s: schemarouter
    • 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)?

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            Oophoo6s Oophoo6s
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration