Replication breaks using XA transaction(one phase) and binlog_format=STATEMENT

Bug #1705151 reported by Jaime Sicam on 2017-07-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.6
Invalid
Undecided
Unassigned
5.7
Triaged
High
Unassigned

Bug Description

Tested on Percona Server 5.7.18:

Test used in https://bugs.mysql.com/bug.php?id=83295

CREATE DATABASE /*! IF NOT EXISTS*/ xatest;
USE xatest;
DROP TABLE IF EXISTS `xatest`;
CREATE TABLE `xatest` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB;
XA START 'xatest';
DELETE FROM xatest where id=1;
XA END 'xatest';
XA COMMIT 'xatest' ONE PHASE;

Replication error:
               Last_SQL_Error: Error 'XAER_RMFAIL: The command cannot be executed when global transaction is in the ACTIVE state' on query. Default database: 'xatest'. Query: 'COMMIT'

Jaime Sicam (jssicam) on 2017-07-19
Changed in percona-server:
status: New → Confirmed

Jaime, please use "Target to Series" and set individual statuses for series

tags: added: upstream
Sveta Smirnova (svetasmirnova) wrote :

Workaround from the upstream bug report: 'And if use `XA PREPARE` (not use `ONE PHASE`), replication error not occurs."

Sveta Smirnova (svetasmirnova) wrote :

Upstream bug fixed in 8.0.4 and 5.7.21

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.