I can confirm another problem - when GTID is used, the slave using wsrep_mysql_replication_bundle > 0, fails with error:
2015-10-19 12:10:16 20849 [ERROR] Slave SQL: When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '12446bf7-3219-11e5-9434-080027079e3d:3707'. Error_code: 1837
2015-10-19 12:10:16 20849 [Warning] Slave: When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '12446bf7-3219-11e5-9434-080027079e3d:3707'. Error_code: 1837
2015-10-19 12:10:16 20849 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.000013' position 10657452
I have used this setting:
percona1 mysql> show variables like 'wsrep_mysql%';
+--------------------------------+-------+
| Variable_name | Value |
+--------------------------------+-------+
| wsrep_mysql_replication_bundle | 50 |
+--------------------------------+-------+
1 row in set (0.01 sec)
I can confirm another problem - when GTID is used, the slave using wsrep_mysql_ replication_ bundle > 0, fails with error:
2015-10-19 12:10:16 20849 [ERROR] Slave SQL: When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '12446bf7- 3219-11e5- 9434-080027079e 3d:3707' . Error_code: 1837 3219-11e5- 9434-080027079e 3d:3707' . Error_code: 1837
2015-10-19 12:10:16 20849 [Warning] Slave: When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '12446bf7-
2015-10-19 12:10:16 20849 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.000013' position 10657452
I have used this setting:
percona1 mysql> show variables like 'wsrep_mysql%'; ------- ------- ------- -----+- ------+ ------- ------- ------- -----+- ------+ replication_ bundle | 50 | ------- ------- ------- -----+- ------+
+------
| Variable_name | Value |
+------
| wsrep_mysql_
+------
1 row in set (0.01 sec)
percona1 mysql> select @@version, @@version_ comment; ------- ------- +------ ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---+ ------- ------- +------ ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---+ ------- ------- +------ ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---+
+------
| @@version | @@version_comment |
+------
| 5.6.26-74.0-56-log | Percona XtraDB Cluster (GPL), Release rel74.0, Revision 1, WSREP version 25.12, wsrep_25.12 |
+------
1 row in set (0.00 sec)
And normal sysbench test: table-engine= InnoDB --mysql-db=test1 --mysql-user=root --oltp- table-size= 6000 --test= /usr/share/ doc/sysbench/ tests/db/ oltp.lua --oltp- tables- count=4 run
[root@db1 ~]# sysbench --db-driver=mysql --test=oltp --mysql-
sysbench 0.5: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
...