Status: Closed (View Workflow)
Affects Version/s: 10.3.29
Fix Version/s: 10.3.32
Environment:3 Node MariaDB / Galera cluster with ProxySQL v2.0.15-20-g32bb92cd proxy in front.
OS: Ubuntu 20.04 LTS
We have a 3 node cluster in our UAT environment, with all traffic going to node 3, an incoming delete conflict causes nodes 1 & 2 to crash. This causes node 3 to go non-primary (as expected).
The crash is always on the non-write nodes (either one of them or both crash) that are applying the deletes concurrently.
the delete is always on the same table named "blobs" with a self-referencing foreign key:
Of note, the logged SQL for the conflict appears to have some garbled data on the end of it (that I can't quite capture in this form):
"SQL: DELETE FROM blobs WHERE id = '7432858'???`^S^F"
The table has been rebuilt with an alter table engine = innodb, yet the issue still occours.
The crashes started 5 days after we upgraded from:
... and on a related note but I must emphasise different cluster entirely; our Production cluster which has yet to be upgraded (version as above) is uttering "[ERROR] InnoDB: Record field 15 len 18446744073709551615" which I've traced back to the same collection of tables in the same schema. I've been unable to identify any corruption in the tables themselves (by selecting out data and forcing index usage). The UAT cluster for which this report relates hasn't uttered these messaged, but I've a sneeking suspicion there is some, even if loose relationship between the issues.
Detail of the crash in the UAT env
node 1 crash:
node 2 crash: