Comment 3 for bug 1250375

Doing it for 5.6 only is better.

Sure if that works. Btw, doesn't ftwrl also do a binlog flush?
On 9 Jan 2014 02:50, "George Ormond Lorch III" <email address hidden>
wrote:

> Raghu, Alexey...I have been asked to get this taken care of and have a
> questions or two:
>
> 1-Is this is only necessary to do within innobackupex::write_galera_info
> if the detected server version is PXC/PS 5.6, or is it harmless to just do
> it regardless of server version as long as --galera_info is specified?
> 2-Would it be acceptable so simply issue 'FLUSH BINARY LOGS; SHOW MASTER
> STATUS' to capture the current binlog filename necessary to backup instead
> of using any extra command line options?
>
> Thanks
>
> --
> You received this bug notification because you are a member of Percona
> core, which is subscribed to Percona XtraBackup.
> https://bugs.launchpad.net/bugs/1250375
>
> Title:
> PXB 56 in galera mode should backup last binlog file
>
> Status in Percona XtraBackup:
> Triaged
> Status in Percona XtraBackup 2.1 series:
> Triaged
> Status in Percona XtraBackup 2.2 series:
> Triaged
>
> Bug description:
> As discussed in https://bugs.launchpad.net/percona-xtradb-
> cluster/+bug/1228304, PXB 5.6 with --galera-info will need to do one
> more step in addition:
>
> a) After it gets uuid and seqno under FTWRL, it needs to do
> 'flush binary logs' and then add the last binlog (after flush) to
> the stream.
>
> b) This is required only if binlog and gtid are enabled on that
> host.
>
> c) The binlog name prefix (ie. XXXX in XXXX.index) can be
> provided through command-line (through an option) if required since that
> is readily
> available to SST script.
>
>
> =================================================================================
>
> This is required for Xtrabackup SST in 5.6 to support gtid (without
> gtid it works fine).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1250375/+subscriptions
>