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

readwritesplitter is not routing queries properly in Maxscale 2.3.2

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 2.3.2
    • 2.2.20, 2.3.4
    • readwritesplit
    • None
    • CentOS 7, Rackspace cloud using OnMetal servers. Percona MySQL 5.6 behind Maxscale and PHP application in front.

    Description

      Upon installing and configuring MaxScale 2.3.2 we encountered errors when slave database (which has read_only=1 set). After investigating it looks like MaxScale is marking all queries as read queries. We have a previous installation running version 2.1.11 which we never saw this issue on. Not a single query was marked as write despite the write queries being simple inserts. Attached is a log that contains queries showing that they are flagged as read.

      Attachments

        1. maxscale.cnf
          2 kB
        2. maxscale-minimal.cnf
          2 kB
        3. querysample_maxscale.log.gz
          14 kB
        4. test_insert1.sql
          0.1 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MXS-2270 MaxScale 2.3 readwritesplit will not route temporary tables to master with leading comments

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              markus makela markus makela
              jparker-resgen Jeffrey Parker
              Votes:
              0 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.