innobackupex: Warning: FLUSH ENGINE LOGS is not supported by the server.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm testing percona-
"innobackupex: Warning: FLUSH ENGINE LOGS is not supported by the server. Data may be inconsistent with binary log coordinates!
Wil the backup have very less chance to be inconsistent when we don't use "FLUSH ENGINE LOGS"? If not, will it be better if we use "FLUSH LOGS" rather than just give a warning when we backup the databases based on mysql-5.1.x?
please give me some advice
BTW,I found that the following source which check the condition to eject the warning is not very correct.
4857 if ($mysql{
should be
4857 if ($mysql{
best regards!
melon
Yes, there's a rather low chance to get inconsistent binary log coordinates when backing up 5.1 servers. Note that data consistency is not affected.
Using FLUSH LOGS instead of FLUSH ENGINE LOGS looks too invasive for a backup utility.
Closing this report as invalid, but thank you for catching this regexp bug in detect_ mysql_capabilit ies_for_ backup( )! Reported separately as bug #1357404.