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

Transaction replay fails when session commands modify the server state inside it

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4
    • Fix Version/s: 2.5.0
    • Component/s: readwritesplit
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-90, MXS-SPRINT-91

      Description

      The following SQL will fail to replay even though the results are similar:

      BEGIN;
      SET autocommit=0;
      INSERT INTO test.t1 VALUES (1);
      

      This is caused by the fact that the state of the session is changed by the set autocommit=0 statement which alters the status bytes the response to the BEGIN returns. The correct way to do this would be to execute any session commands inside the transaction in the same order the appeared in.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: