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

change master to master_use_gtid= purges relay log and fetchs binlog from master

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.0.21
    • N/A
    • Replication
    • None

    Description

      when STOP SLAVE; CHANGE MASTER TO MASTER_USE_GTID=

      {slave_pos|current_pos}

      ; START SLAVE is used, the relay logs are purged and refetched from the master. In this case, or when the gtid_slave_pos is advanced, the relay logs will contain all the transactions required to continue.

      As I discovered when doing when a replication delay exceeded expire_log_days of the master was that I was left in a state with no relay logs and a master file:position that wasn't able to be fetched.

      An ideal implementation would examine to see at what point the existing relay logs can be used to continue replication.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-4698 With GTID replication, relay logs cannot be relied upon while purging binary logs on master

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-8945 Avoid overloading the master NIC on restarting IO_THREAD on lagging slave.

          • Major - Major loss of function.
          • Open

          Activity

            People

              knielsen Kristian Nielsen
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.