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

Error "The MariaDB server is running with the --read-only option" for "select for update"

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.9
    • 2.2.15
    • readwritesplit
    • None
    • Cent OS
    • MXS-SPRINT-66, MXS-SPRINT-67

    Description

      Under some circumstances, Maxscale route a "select .. for update" the the slave.

      If slave is read only, this error message will be returned.

      2018-09-04 13:01:04 info : (8846688) [readwritesplit] > Autocommit: [enabled], trx is [not open], cmd: (0x03) COM_QUERY, plen: 127, type: QUERY_TYPE_READ, stmt: select * from tablename _locks where name = 'somewhat' 
      2018-09-04 13:01:04 info : (8846688) [readwritesplit] Route query to slave [127.0.0.1]:6603 <
      

      ERROR 1290 (HY000) at line 1: The MariaDB server is running with the --read-only option so it cannot execute this statement [maxscale@server maxscale_logs]$
      

      Especially with autocommit enabled the error message makes no sense.

      " autocommit is set to 1, the LOCK IN SHARE MODE and FOR UPDATE clauses have no effect."
      Knowledge Bse for update

      Attachments

        Activity

          People

            johan.wikman Johan Wikman
            Richard Richard Stracke
            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.