Comment 7 for bug 1158221

Revision history for this message
Marc Castrovinci (marc-castrovinci) wrote :

I've also received the same error with versions:
5.6.15-63.0-log Percona XtraDB Cluster (GPL), Release 25.5, wsrep_25.5.r4061

*** Priority TRANSACTION:
TRANSACTION 1162252, ACTIVE 1 sec setting table lock for creating or dropping index
mysql tables in use 1, locked 1
MySQL thread id 31, OS thread handle 0x7f7fd764e700, query id 6777827 committing alter table to storage engine
alter table XXXXX modify column XXXXXXXXX VARCHAR(36) NULL DEFAULT NULL

*** Priority TRANSACTION:
TRANSACTION 1162281, ACTIVE 1 sec
14 lock struct(s), heap size 3112, 12 row lock(s), undo log entries 4
MySQL thread id 20, OS thread handle 0x7f7fd97fd700, query id 6777852 applied write set 1000902
*** WAITING FOR THIS LOCK TO BE GRANTED:
TABLE LOCK table `XXXXX`.`XXXXXX` trx id 1162281 lock mode IS
2014-07-08 03:54:48 29960 [Note] WSREP: cluster conflict due to high priority abort for threads:
2014-07-08 03:54:48 29960 [Note] WSREP: Winning thread:
   THD: 31, mode: applier, state: executing, conflict: no conflict, seqno: 1000898
   SQL: alter table XXXXXX modify column XXXXXXX VARCHAR(36) NULL DEFAULT NULL
2014-07-08 03:54:48 29960 [Note] WSREP: Victim thread:
   THD: 20, mode: applier, state: idle, conflict: no conflict, seqno: 1000902
   SQL: (null)
2014-07-08 03:54:48 29960 [ERROR] WSREP: Trx 1000898 tries to abort slave trx 1000902. This could be caused by:
        1) unsupported configuration options combination, please check documentation.
        2) a bug in the code.
        3) a database corruption.
 Node consistency compromized, need to abort. Restart the node to resync with cluster.
03:54:48 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster