Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28609

refine gtid-strict-mode to ignore same server-id gtid from the past on semisync slave

    XMLWordPrintable

    Details

      Description

      To provide semisync master crash-recovery (MDEV-21117) the same server-id transactions
      were made to accept for execution on the semisync slave when the strict gtid
      mode (see MDEV-27760).
      That however caused out-of-order error on a master's transaction
      server of the circular setup.
      The error was fair in the sense of the gtid strict mode rule as indeed
      under the condition of the circular setup the replicated transaction
      already exists in the local binlog.

      This gets fixed to ignore on the gtid strict mode semisync
      slave those gtids that exist in the slave's binlog that effectively restores
      the default same-server-id ignore policy on the semisync slave.
      At the same time the fixes complies with MDEV-21117 semisync slave recovery
      to accept the same server-id transactions that do not exist in local binlog.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Elkin Andrei Elkin
              Reporter:
              Elkin Andrei Elkin
              Votes:
              2 Vote for this issue
              Watchers:
              10 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.