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

LP:697174 - mysqldump --single-transaction in maria-5.1-mwl136 uses an absolute path to master_log_file in CHANGE MASTER

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      When using mysqldump --single-transaction --master data, the following CHANGE MASTER is produced:

      CHANGE MASTER TO MASTER_LOG_FILE='/home/philips/bzr/maria-5.1-mwl136/mysql-test/var/log/master-bin.000001', MASTER_LOG_POS=1255946;

      Using absolute paths for MASTER_LOG_FILE will cause the slave to stop with a "cannot open first file" error. By contrast, normal mysqldump would return:

      CHANGE MASTER TO MASTER_LOG_FILE='master-bin.000001', MASTER_LOG_POS=1255946;

      To reproduce:

      1. default mysqldump from RPM
        mysqldump --single-transaction --master-data -uroot --protocol=tcp --port=19300 test | grep -i change
        CHANGE MASTER TO MASTER_LOG_FILE='master-bin.000001', MASTER_LOG_POS=1255946;
      1. mysqldump from wl139
        ../client/mysqldump --single-transaction --master-data -uroot --protocol=tcp --port=19300 test | grep -i change
        CHANGE MASTER TO MASTER_LOG_FILE='/home/philips/bzr/maria-5.1-mwl136/mysql-test/var/log/master-bin.000001', MASTER_LOG_POS=1255946;

      ../client/mysqldump --master-data -uroot --protocol=tcp --port=19300 test | grep -i change
      CHANGE MASTER TO MASTER_LOG_FILE='master-bin.000001', MASTER_LOG_POS=1255946;

      Attachments

        Activity

          People

            knielsen Kristian Nielsen
            philipstoev Philip Stoev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 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.