"FLUSH TABLE" is written to the binary log

[Julien Pivotto]

The latest release of Xtrabackup issues a FLUSH TABLE before the FTWRL.
While it will help the backups in some situation, it also implies that
FLUSH TABLE will be written to the binary log.

While this situation is okay most of the time, it is not in MariaDB 10.0
with GTID enabled. If the backup is taken on the Slave, then the FLUSH
TABLE statement is still written to the binary log. This alters the GTID
of that slave and XtraBackup does not see the "correct" GTID anymore.

It is then impossible to see the GTID of the backup, because we would
only see the "wrong" GTID that was written to the binary log.

To avoid that, we have to issue the flush command with the
NO_WRITE_TO_BINLOG option.

Side note 1:
Our setup: MariaDB 10.0; GTID Replication, with GTID strict mode, and
log-slave-updates=0.

Side note 2:
There is no problem with the FTWRL because it is never written to the
binlog.

[Julien Pivotto (roidelapluie)]

Fix is in https://github.com/percona/percona-xtrabackup/pull/72

[Sergei Glushchenko (sergei.glushchenko)]

Fix for 2.3 https://github.com/percona/percona-xtrabackup/pull/78

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-728