xtrabackup_info binlog_pos GTID splitting to multiple lines
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Triaged
|
Medium
|
Unassigned | |||
2.4 |
Triaged
|
Medium
|
Unassigned |
Bug Description
Getting a snapshot from a database in a Percona server (configured for Fabric) results in a "binlog_pos = GTID of the last change" that breaks up into multiple lines when there are multiple GTID ranges specified.
Specifically, running a snapshot using the following command:
innobackupex --host=127.0.0.1 --user=root --password=$p --rsync --safe-slave-backup --slave-info /var/backups/
sdir=$(ls -1 | egrep "^$sdate")
innobackupex --host=127.0.0.1 --user=root --password=$p --apply-log /var/backups/
the resulting xtrabackup_info file contains these 2 lines:
binlog_pos = GTID of the last change 'f43a8a6b-
f465b62d-
-note that the white-space after the comma has been reinterpreted as a carriage return, only in xtrabackup_info.
In xtrabackup_
SET GLOBAL gtid_purged=
-versions:
Percona Server Release 72.1 Revision 0503478
xtrabackup version 2.2.10 based on MySQL server 5.6.22 Linux (x86_64) (revision id: )
innobackupex version: InnoDB Backup Utility v1.5.1-xtrabackup
affects: | percona-server → percona-xtrabackup |
description: | updated |
It should be added that the snapshot works fine after setting GTID_purged to
'f43a8a6b- c136-11e4- b41c-f23c9133c3 56:1-219456761, f465b62d- f288-11e4- b5b8-f23c91189b e4:1-39'
and that the machine it was generated on was an active slave receiving transactions at that time.