Percona XtraBackup moved to https://jira.percona.com/projects/PXB

innobackupex should skip GTID output is GTID_MODE is OFF

Bug #1391041 reported by Jervin R
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Medium
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.3.1-beta1
2.1
Won't Fix
Undecided
Unassigned
2.2
Fix Released
Medium
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.7
2.3
Fix Released
Medium
Sergei Glushchenko
Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.3.1-beta1

Bug Description

Below are log outputs from different backups on the same server with GTID mode is OFF - the GTID part can cause confusion since its none incrementing.

innobackupex: MySQL binlog position: filename 'mysql-bin.000287', position 431329357, gtid_executed 72be0aa4-3988-11e4-bf5a-0cc47a08e7b0:1-213

innobackupex: MySQL binlog position: filename 'mysql-bin.000287', position 463378077, gtid_executed 72be0aa4-3988-11e4-bf5a-0cc47a08e7b0:1-213

Related branches

lp://staging/~sergei.glushchenko/percona-xtrabackup/2.2-xb-bug1391041
Alexey Kopytov (community): Approve
Diff: 191 lines (+95/-12)
6 files modified
storage/innobase/xtrabackup/doc/source/howtos/recipes_ibkx_gtid.rst (+2/-2)
storage/innobase/xtrabackup/innobackupex.pl (+16/-6)
storage/innobase/xtrabackup/test/t/bug1391041.sh (+73/-0)
storage/innobase/xtrabackup/test/t/bug977101.sh (+2/-2)
storage/innobase/xtrabackup/test/t/gtid.sh (+1/-1)
storage/innobase/xtrabackup/test/t/ib_slave_info.sh (+1/-1)
lp://staging/~sergei.glushchenko/percona-xtrabackup/2.3-xb-bug1391041
Alexey Kopytov (community): Approve
Diff: 191 lines (+95/-12)
6 files modified
storage/innobase/xtrabackup/doc/source/howtos/recipes_ibkx_gtid.rst (+2/-2)
storage/innobase/xtrabackup/innobackupex.pl (+16/-6)
storage/innobase/xtrabackup/test/t/bug1391041.sh (+73/-0)
storage/innobase/xtrabackup/test/t/bug977101.sh (+2/-2)
storage/innobase/xtrabackup/test/t/gtid.sh (+1/-1)
storage/innobase/xtrabackup/test/t/ib_slave_info.sh (+1/-1)
Revision history for this message
Nilnandan Joshi (nilnandan-joshi) wrote :

Able to reproduce the same. I would agree that if GTID_MODE=OFF then it should not covered while backup.

innobackupex: Backup created in directory '/home/nilnandan/backup/2014-11-13_13-46-00'
innobackupex: MySQL binlog position: filename 'mysql-bin.000003', position 338, GTID of the last change 'd05ede31-5361-11e4-a7e9-4ceb42171cea:1-6'
141113 13:46:28 innobackupex: Connection to database server closed
141113 13:46:28 innobackupex: completed OK!
nilnandan@Dell-XPS:~$

innobackupex: Backup created in directory '/home/nilnandan/backup/2014-11-13_13-47-32'
innobackupex: MySQL binlog position: filename 'mysql-bin.000003', position 637, GTID of the last change 'd05ede31-5361-11e4-a7e9-4ceb42171cea:1-6'
141113 13:48:00 innobackupex: Connection to database server closed
141113 13:48:00 innobackupex: completed OK!
nilnandan@Dell-XPS:~$

Changed in percona-xtrabackup:
status: New → Confirmed
Revision history for this message
Alexey Kopytov (akopytov) wrote :

It also makes sense to fix the opposite case: skip non-GTID coordinates when GTID mode is enabled. It is important for multi-threaded slaves, because GTID is the only reliable slave state source for MTS.

I had plans to implement that for the next release. Let's keep this report to fix both GTID and non-GTID cases.

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-712

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

Other bug subscribers

Remote bug watches

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