GTID support for MariaDB server

[Nirbhay Choubey]

As mentioned in lp:1326967, there are some variables used in innobackupex
which are not present in MariaDB server.

The attached patch fixes the same.

Verified on PXC-5.6, MGC-10.0.

PS: This patch also includes the patch for lp:1326967.

[Nirbhay Choubey (nirbhay)]

Addressed Kristian's suggestions to include values of all the
GTID variables as they might be needed in different provisioning
scenarios.

[Alexey Kopytov (akopytov)]

Thanks for the contribution. The patch will be merged in the next release.

[Viacheslav Chernyshev (astellar)]

I have downloaded patch from post #2 and applied it to innobackupex from 2.2.3 release. After that I've tried to take a backup from our MariaDB 10.0.12 server. And results are somewhat strange. After successful backup I receive this info: "MySQL binlog position: filename 'mariadb-bin.000177', position 369748838, gtid_slave_pos #, gtid_binlog_state 0-111-67882056, gtid_current_pos 0-111-67882056, gtid_binlog_pos 0-111-67882056". However, SELECT BINLOG_GTID_POS("mariadb-bin.000177", 369748838) reports '0-111-67882285.

[Nirbhay Choubey (nirbhay)]

Updated patch with a fix for issue reported in comment#4. The patch now defers the retrieval of GTID values after FTWRL.

[Nirbhay Choubey (nirbhay)]

Thanks for trying out the patch and reporting the issue. Can you please try the latest patch (v3)
and let us know if it fixes the problem?

[Viacheslav Chernyshev (astellar)]

Tested v3 of this patch today. It seems that problem still exists.

Report from innobackupex:
innobackupex: MySQL binlog position: filename 'mariadb-bin.000634', position 916489279, gtid_slave_pos #, gtid_binlog_state 0-111-176382402, gtid_current_pos 0-111-176382402, gtid_binlog_pos 0-111-176382402

Result of SELECT BINLOG_GTID_POS('mariadb-bin.000634', 916489279):
0-111-176769796

[Nirbhay Choubey (nirbhay)]

Could you share the command you executed to take the backup?

[Viacheslav Chernyshev (astellar)]

Yes, I use streaming backup this way:
innobackupex --user=xxx --password=yyy --stream=tar ./ | pigz -c | nc some_host some_port

[Nirbhay Choubey (nirbhay)]

Ok, this time I was able to reproduce this issue. The attached patch should fix it (innobackupex_1329539_v4.diff).

[Shahriyar Rzayev (rzayev-sehriyar)]

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