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

Mariadb-dump --delete-master-logs May Not Delete Binary Logs

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
    • 10.5, 10.6, 10.11
    • Replication, Scripts & Clients
    • None

    Description

      Because --delete-master-logs immediately purges logs after flushing, if there are any active dump threads on the master, they may still be using the old binary log when the purge executes, disallowing the file from being deleted.

      Workarounds are either to manually re-run PURGE BINARY LOGS TO once the dump threads have caught up, or to temporarily disconnect replicas before performing the dump.

      Test case 8 in mysql-test/main/rpl_mysqldump_slave.test implements the second work-around for consistent behavior to pass. Depending on the resolution of this ticket, that test may need to be fixed to remove the work-around.

      Attachments

        Issue Links

          split from

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32953 main.rpl_mysqldump_slave Fails with "Master binlog wasn't deleted" Assertion

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

          Activity

            People

              bnestere Brandon Nesterenko
              bnestere Brandon Nesterenko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.