[MDEV-30323] Some DDLs like ANALYZE can complete on parallel slave out of order Created: 2023-01-02  Updated: 2023-04-02  Resolved: 2023-01-24

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10
Fix Version/s: 10.3.38, 10.4.28, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3

Type: Bug Priority: Critical
Reporter: Andrei Elkin Assignee: Andrei Elkin
Resolution: Fixed Votes: 0
Labels: parallelslave

Issue Links:
Duplicate

 Description   

ANALYZE TABLE can complete on slave before a preceding transaction does so. E.g in case
of the binlogging slave and the strict gtid mode something like the following error 

Last_SQL_Error: An attempt was made to binlog GTID 812700-812700-487719 which would create an out-of-order sequence number with existing GTID 812700-812700-487721, and gtid strict mode is enabled

may occur. In the specific paste above GTID 812700-812700-487721 corresponds to ANALYZE, and GTID 812700-812700-487719 to a regular BEGIN..COMMIT transaction binlogged earlier.
The error indicates the transaction binlogging on slave violates the master binlog order.

The reason of the failure has been identified as a flaw introduced by MDEV-17515.

 Comments   
Comment by Andrei Elkin [ 2023-01-09 ]

Howdy Brandon.

The fixes
2fc172c7ac9...7c45051be88 HEAD -> bb-10.2-andrei (forced update)
are waiting for your review.

Cheers,

Andrei

Comment by Brandon Nesterenko [ 2023-01-18 ]

Left some notes on the GitHub patch 7c45051 and discussed on Slack

Generated at Thu Feb 08 10:15:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.