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

Galera system variables are not parsed by the embedded server

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0.5
    • Fix Version/s: 1.4.1
    • Component/s: Plugin, readwritesplit
    • Labels:
      None
    • Environment:
      All OS

      Description

      This is import of bug http://bugs.mariadb.com/show_bug.cgi?id=699

      [[Kolbe Kegel 2015-01-16 18:38:15 UTC]]
      I opened bug #509 some time ago, but that bug was handled specifically for the case of last_insert_id(). The crux of that bug still exists in 1.0.4 GA:

      [root@max1 ~]# mysql -h 127.0.0.1 -P 4006 -u maxuser -pmaxpwd -e 'select @@hostname, @@wsrep_node_name; select @@wsrep_node_name, @@hostname;'
      +------------+-------------------+
      | @@hostname | @@wsrep_node_name |
      +------------+-------------------+
      | db2        | db2               |
      +------------+-------------------+
      +-------------------+------------+
      | @@wsrep_node_name | @@hostname |
      +-------------------+------------+
      | db3               | db3        |
      +-------------------+------------+
      

      In a single connection, fetching the values of the same two system variables results in the query being routed differently depending on the order of the variables.

      Is there some set of variables that should always be routed to the master for some reason? If so, that should be documented.

      Regardless, the order of terms in the SELECT list should not have any effect on query routing.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Massimiliano Pinto Massimiliano Pinto (Inactive)
              Reporter:
              kolbe Kolbe Kegel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: