Details
Description
GTID sequence drifts between Write node and appliers node by issueing some KILL QUERY statements on a Galera node which is operating user's transactions.
Data consistency is maintained and wsrep_last_committed is in sync.
NOTE: It's not always sufficient to issue one single KILL QUERY, I should do more fine grained research to determine what are the specific circumstances, in my current tests I reproduced it by killing some random mysqlslap queries.
GTID sequence de-alignment breaks among others maxscale auto-failover.
To make things more complicated in the current attached pictures test Writer is behind but in other tests Writer went ahead(see attached txt for 2nd test)
Attachments
Issue Links
- is part of
-
MDEV-29293 MariaDB stuck on starting commit state (waiting on commit order critical section)
-
- Closed
-
If there was some issue with KILL and GTID it was fixed on
MDEV-29293. However there is repeatable test case with INSERT IGNORE with duplicate key causing GTID sequence breakage and there is also problem with INSERT with at least one successful write and one duplicate key.