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

mysqldump can't save master position without stopping the slave during the entire dump

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.1.38
    • 10.1
    • Backup, Replication
    • None

    Description

      Goal: take a mysqldump of a running server with it's master's coordinates saved in the dump in order to be able to use the dump to rebuild a slave. Do this without stopping the slave.

      Problem: there is an option --dump-slave=2, but to my dismay this will stop the SQL slave thread the entire time. Why is this needed? And, furthermore - with such option, if you kill (gracefully. kill -15) the mysqldump process, the slave is left in the stopped state...

      Please, make it possible to take a dump of a running slave with master's coordinates, without having to stop it.

      Command used:

      mysqldump --single-transaction --routines --triggers --dump-slave=2 -A .....

      Attachments

        Activity

          People

            Elkin Andrei Elkin
            rpizzi Rick Pizzi
            Votes:
            1 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.