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

            Activity

              People

              Assignee:
              KennethDyer Kenneth Dyer
              Reporter:
              claudio.nanni Claudio Nanni
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: