percona xtrabackup 2.2.4 innobackup FLUSH ENGINE LOGS
Bug #1384140 reported by
sam
This bug report is a duplicate of:
Bug #1394632: "FLUSH ENGINE LOGS" bring inconsistency into GTID-enabled slave.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
when I backup mysql5.6.19 on slave with percona-xtrabackup 2.2.4,I find that innobackupex executes the command:
FLUSH ENGINE LOGS
this command will be record to slave binlog,which leads to inconsistency between master and slave
NOw,I have update the innobackupex file ,as follows:
replace the line :
mysql_query(
with
mysql_query(
I have test it,and now do not record "FLUSH ENGINE LOGS" to slave binlog
that 'all,thank you
Tags: None
information type: | Private Security → Public |
To post a comment you must log in.
I wonder why this bug is marked as "Private" and should it remain private? Also, what inconsistency extra FLUSH ENGINE LOGS may cause, for real data?