Bug #72952 when GTID is too long, apply-log truncate GTID by 4080 characters after
Submitted: 11 Jun 2014 8:41 Modified: 15 Jul 2014 18:14
Reporter: Tac Huang Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S2 (Serious)
Version:3.9.0, 3.11.0 OS:Linux
Assigned to: CPU Architecture:Any
Tags: GTID

[11 Jun 2014 8:41] Tac Huang 
Description:
When GTID is too long, apply-log will warn as following:

 mysqlbackup: WARNING: Unknown meta variable name found and ignored
.  Meta file path = /home/ACTIONTECH-HA/mysql-install/full-dir/meta/backup_variables.txt
   Variable name = 1761,ddc72234-f12b-11e3-a77f-080027956067:1-8

and GTID in backup_gtid_executed.sql will be truncated by 4080 characters

How to repeat:
(see attached log)

1. set GTID_PURGED to a long GTID (>4080 character)

2. make a full backup by mysqlbackup

3. verify the GTID in backup_gtid_executed.sql is OK

4. image-to-backup-dir the full backup

5. verify the GTID in backup_gtid_executed.sql is OK

6. apply-log

7. verify the GTID in backup_gtid_executed.sql is truncated

Suggested fix:
Maybe it's limited by backup variables length.
[11 Jun 2014 8:41] Tac Huang 
attached detail log

Attachment: meb.log (application/octet-stream, text), 31.67 KiB.
[15 Jul 2014 18:14] Sveta Smirnova 
Thank you for the report.

Verified as described with exception that I used simple backup command:

mysqlbackup --user=root --host=127.0.0.1 --port=13000 --backup-dir=/home/sveta/src/BACKUPDIR/bug72952 backup
[2 Mar 2015 21:36] Sveta Smirnova 
Posted by developer:
 
Bug is not repeatable with version 3.12.0