On a fresh new master-slave very simple setup with just a Magento 1.5 DB under MySQL 5.6.35, I'm getting this error with a memory table:
2017-05-03 07:08:37 1109 [Note] Slave I/O thread: connected to master 'replica@10.0.15.183:3306',replication started in log 'FIRST' at position 4 2017-05-03 11:38:18 1109 [ERROR] Slave SQL: Error '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 '76a1eb3e-1ecc-11e7-a106-027ba847acd7:121'.' on query. Default database: 'xxxxx_web'. Query: 'DELETE FROM `xxxxx_web`.`catalog_product_index_price_bundle_tmp`', Error_code: 1837 2017-05-03 11:38:18 1109 [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 '76a1eb3e-1ecc-11e7-a106-027ba847acd7:121'. Error_code: 1837 2017-05-03 11:38:18 1109 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'xxxxx-pre-master-mysql-bin.000001' position 68789
and replication stops util I stop/start slave.
That looks it was fixed in https://bugs.mysql.com/bug.php?id=68525 but it's happening to me at least.
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!