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

Crash on transaction replay if log_info is on and session starts with no master

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Trivial
    • Resolution: Fixed
    • 2.3.5
    • 2.3.6
    • readwritesplit
    • None

    Description

      When configured with transaction_replay=true and log_info enabled, if a session started without a master and later on a master would become available the next start of a transaction would trigger a transaction migration. The transaction migration code unconditionally used the old master's name and if no master was available, the master reference was not valid.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            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.