Perhaps this is just part of a known limitation with Galera with tables without primary keys. Going back to our developers to have them add a primary key to the table to see if that resolves our particular issue.
I am running 5.5.37-MariaDB-wsrep MariaDB Server, wsrep_25.10.r3980 on CentOS
Here is the error log output:
BF-BF X lock conflict
RECORD LOCKS space id 758201 page no 3 n bits 192 index `GEN_CLUST_INDEX` of table `aviationweek`.`penton_magazine_order_items` trx id 13D07782 lock_mode X locks rec but not gap
140620 10:09:30 [ERROR] mysqld got signal 6 ;
The table in question has no primary key;
CREATE TABLE `penton_magazine_order_items` (
`list_id` int(10) unsigned NOT NULL,
`article_id` int(10) unsigned NOT NULL,
`weight` int(11) NOT NULL DEFAULT '0',
`weight_in_issue` int(11) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8
There have been bug reports of similar problems here
and perhaps here
I will report back here if adding a PK to the table makes this issue go away.