Bug #87130 XA COMMIT not taken as transaction boundary
Submitted: 20 Jul 2017 3:46 Modified: 20 Jul 2017 15:27
Reporter: Wei Zhao (OCA) Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: XA transactions Severity:S2 (Serious)
Version:5.7.17 OS:Any
Assigned to: CPU Architecture:Any

[20 Jul 2017 3:46] Wei Zhao
XA COMMIT is not taken as a transaction boundary in Transaction_boundary_parser::get_event_boundary_type() and Query_log_event::ends_group()

This is obviously wrong, and it caused several bugs in binlog replication when there are XA event groups replicated.

How to repeat:
run binlog replication with XA event groups.

Suggested fix:
See my patch.
[20 Jul 2017 3:47] Wei Zhao
this patch fixes the bug

Attachment: txn-boundary.diff (application/octet-stream, text), 1.58 KiB.

[20 Jul 2017 15:27] MySQL Verification Team

I completely agree with both your analysis and your patch. Thank you for your contribution.

Verified as reported.
[17 Nov 2017 1:53] Wei Zhao
adding the patch as contribution

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: txn-boundary.diff (application/octet-stream, text), 1.58 KiB.

[17 Nov 2017 12:58] MySQL Verification Team
Hi Wei,

Thank you very much for your contribution.