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

GTID current_pos easily breaks replication

    XMLWordPrintable

Details

    Description

      Replication using GTID and MASTER_USE_GTID=current_pos easily breaks when a transaction is generated on the Slave and Replication is restarted.
      It happens if the transaction generated on the Slave is the last before issuing START SLAVE,
      so even after the replication was already stopped.
      To recover you need to switch to slave_pos gtid mode.
      Test attached.
      I also noticed a non consistent numbering of GTID, but it's not related, the trx_num part of GTID for transactions generated on the Slave is increased by one in respect to trx_num of the latest GTID received from the Master.

      So you can have:

      1-100-1000
      1-100-1001
      1-100-1002
      1-200-1003
      1-200-1004
      1-100-1003
      1-100-1004

      I don't know if it's on purpose, but it does not seem consistent to me, at first impression I'd make each server having its own trx numbering with no holes.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21687 When creating a table in the master database, and then executing stop slave, add index, start slave in the slave database; a replication error occurred from the slave ; but there was no exception in mysql

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-10279 gtid_current_pos is not updated with slave transactions from old master

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17156 Local transactions on a Slave don't update GTID's gtid_current_pos after RESET MASTER on Slave (master_use_gtid value is not relevant)

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20122 Deprecate MASTER_USE_GTID=Current_Pos to favor new MASTER_DEMOTE_TO_SLAVE option

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              KennethDyer Kenneth Dyer (Inactive)
              claudio.nanni Claudio Nanni
              Votes:
              1 Vote for this issue
              Watchers:
              5 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.