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

Simple sharding tutorial is out of date

    XMLWordPrintable

Details

    • MXS-SPRINT-208

    Description

      The simple sharding tutorial is out of date as it does not mention that auth_all_servers must be enabled. In MaxScale 6, it must be enabled manually as the schemarouter no longer modifies the service configuration directly.

      Original title:
      connection to shard should work with mariadb client tools

      Original description:
      When I run these tests against MaxScale with SchemaRouter I get errors in some cases (as the documentation states):

      mariadb --user=app --password=secret --host=10.153.125.219 --port=3306
      mariadb --user=app --password=secret --host=10.153.125.219 --port=3306 --database=customer_0010
      mariadb --user=app --password=secret --host=10.153.125.219 --port=3306 --database=customer_0020
      ERROR 1049 (42000): Unknown database 'customer_0020'
      mariadb --user=app --password=secret --host=10.153.125.219 --port=3306 --execute='use customer_0020'
      mariadb --user=app --password=secret --host=10.153.125.219 --port=3306 customer_0010
      mariadb --user=app --password=secret --host=10.153.125.219 --port=3306 customer_0020
      ERROR 1049 (42000): Unknown database 'customer_0020'

      But in theses (erroneous) cases MaxScale exactly knows where to route me.

      So for compatibility reasons MaxScale should behave like a normal database and route me correctly to the target shard.

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              oli Oli Sennhauser
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.