When GTID_MODE=ON and slave uses MASTER_AUTO_POSITION=0, GTID is used in --slave-info

Bug #1705193 reported by Vasily Nemkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.3
Fix Released
High
Vasily Nemkov
2.4
Fix Released
High
Vasily Nemkov

Bug Description

Copied from here: https://jira.percona.com/browse/PXB-193

When running xtrabackup --backup --slave-info I am getting a gtid, even though master_auto_position=0:

[root@perconaserver vagrant]# cat xtrabackup_backupfiles/xtrabackup_slave_info
SET GLOBAL gtid_purged='ad1ce570-f9d1-11e6-b066-08002789cd2e:1';
CHANGE MASTER TO MASTER_AUTO_POSITION=1

I am running:

    pxb 2.4.7
    percona server 5.7.18
    gtid_mode=on, master_auto_position=0
    running xtrabackup --backup --slave-info

I would expect as master_auto_position=0 that the backup uses the standard file and position OR have both options available all the time.

Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :
Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :
Revision history for this message
Vasily Nemkov (vasily.nemkov) wrote :

PXB used to determine GTID mode on slave incorrectly, and thus generated invalid xtrabackup_slave_info.

For MariaDB PXB used `gtid_slave_pos` variable, now we use `Using_Gtid` from `SHOW SLAVE STATUS`.
For MySQL PXB used `Executed_Gtid_Set` instead of correct `Auto_Position` from `SHOW SLAVE STATUS`.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-505

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.