[MXS-3953] Transaction start written to binlog prematurely Created: 2022-01-20  Updated: 2022-06-03  Resolved: 2022-01-28

Status: Closed
Project: MariaDB MaxScale
Component/s: pinloki
Affects Version/s: 2.5.18, 6.2.1
Fix Version/s: 6.2.2

Type: Bug Priority: Major
Reporter: Niclas Antti Assignee: Niclas Antti
Resolution: Fixed Votes: 1
Labels: None


 Description   

When a transaction starts, the "transaction-start" is immediately written to the binlog. If maxscale is killed before the full txn is received, the "transaction-start" will (eventually) be duplicated in the log. A connected mariadb replica may fail in some circumstances.


Generated at Thu Feb 08 04:25:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.