[#MDEV-31503] ALTER SEQUENCE ends up in optimistic parallel slave binlog out-of-order

2023-06-01  0:00:00 9 [ERROR] Slave SQL: Error 'An attempt was made to binlog GTID 1-1-213122284 which would create an out-of-order sequence number with existing GTID 1-1-213122286, and gtid strict mode is enabled' on query. Default database: 'xxxx'. Query: 'Alter Sequence seq_xxxx Restart With 1', Gtid 1-1-213122284, Internal MariaDB error code: 1950

2023-06-01  0:00:00 9 [Warning] Slave: An attempt was made to binlog GTID 1-1-213122284 which would create an out-of-order sequence number with existing GTID 1-1-213122286, and gtid strict mode is enabled Error_code: 1950

2023-06-01  0:00:00 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

This bug was supposed to be fixed in the intermediate MariaDB ES release 10.6.12-8.
But seems like the customer is still facing the issue.

[MDEV-31503] ALTER SEQUENCE ends up in optimistic parallel slave binlog out-of-order Created: 2023-06-20 Updated: 2023-09-08 Resolved: 2023-07-14
Status:	Closed
Project:	MariaDB Server
Component/s:	Replication
Affects Version/s:	10.6.12
Fix Version/s:	10.8.8, 10.4.31, 10.5.22, 10.6.15, 10.9.8, 10.10.6, 10.11.5, 11.0.3, 11.1.2

[MDEV-31503] ALTER SEQUENCE ends up in optimistic parallel slave binlog out-of-order Created: 2023-06-20 Updated: 2023-09-08 Resolved: 2023-07-14