Updating data causes PXC Crash


We have three node XtraDB cluster, the cluster was working fine for past few weeks. Today our cluster completely crashed, while checking the logs I found this issue created due to the update. Please find the error below and the complete stack trace inattachment. Any idea why the insertion failure leads to complete cluster crash.

Thanks in advance for your help.

130409 8:07:21 [Note] WSREP: cleaning up ec4f0d2c-a0f1-11e2-0800-b39cacad59c1 (tcp: //
len 224; hex a85432b5662b0000792f2fea652b000000fc0d8c622b0000000000000000 000000000000000000000000000000000000030000000000000002000000 000000000100000000000000000000000000000000000000000000000000 00000000000001000000000000000000000000000000b1dbfe8c8d48a225 000000000000000001000000000000008344510700000000deaf2f2c0000 00000200000000000000010000000000000000fc0d8c622b0000e2cd0000 0000000060e1117700000000020000000000000058471c60622b0000d8af 2f2c000000001800000000000000; asc T2 f+ y// e+ b+ H % DQ /, b+ w XGb+ /, ;
TRANSACTION 3844623, ACTIVE 0 sec fetching rows
mysql tables in use 2, locked 1
69 lock struct(s), heap size 14776, 181 row lock(s), undo log entries 6
MySQL thread id 2214011, OS thread handle 0x2b66b20b1940, query id 84509749 dbadmin preparing
UPDATE news SET app_status = ‘D’, load_status = ‘D’ WHERE ( guid IN (SELECT DISTINCT gallery_id FROM gallery WHERE app_status=‘A’ OR app_status=‘N’) AND feed_id !=21)
130409 8:07:35 InnoDB: Assertion failure in thread 47720073730368 in file btr0pcur.c line 257

Hello, could you please show us the show creta table of news and gallery?

Also it would be useful to know if you can reproduce this error (in a test environment) and what is the package version.

BTW, where is the full stack trace?


Martin Arrieta