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

Session state changed inside a read-only transaction is not applied on all servers

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 23.02, 23.08, 24.02, 25.01, 25.10, 26.10
    • N/A
    • Core
    • None
    • Can result in unexpected behaviour

    Description

      If a client changes the state of the session while a read-only transaction is open, the change is only made on the server the transaction is running on. The other servers are left as they were, also after the transaction has ended. This applies to statements such as SET and USE, and to changing the user and resetting the connection. With readwritesplit, after a USE inside a read-only transaction, reads are made in the new database but writes, which go to the primary, in the old one. After a change of user, the statements routed to the primary are executed as the previous user.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.