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

use_sql_variables_in=master can break functionality of important session variables

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.1
    • 2.0.2
    • readwritesplit
    • None
    • 2016-22

    Description

      When use_sql_variables_in=master, the ReadWriteSplit router will route queries like the following only to the master:

      SET SESSION wsrep_sync_wait=1;
      

      In this specific case, it's very important that wsrep_sync_wait get set on the slaves. If the variable is only routed to the master, the application might see errors when queries don't return the expected results.

      https://mariadb.com/kb/en/mariadb/galera-cluster-system-variables/#wsrep_sync_wait

      Possible fixes:

      • Only let use_sql_variables_in affect user-defined variables, not system variables.
      • Only let use_sql_variables_in affect queries that read variables, not queries that write variables with SET.

      Attachments

        Activity

          People

            markus makela markus makela
            GeoffMontee Geoff Montee (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 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.