Update Query Crashes server

[mv_xtradb]

Hello,

The update query crashes the server, it happened twice but is not repeatable.

130409 8:07:15 [Note] WSREP: Flow-control interval: [23, 23]
130409 8:07:15 [Note] WSREP: New cluster view: global state: 676cabb4-9c37-11e2-0800-1b878d60438a:12510993, view# 26: Primary, number of nodes: 2, my index: 1, protocol version 2
130409 8:07:15 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
130409 8:07:15 [Note] WSREP: Assign initial position for certification: 12510993, protocol version: 2
130409 8:07:15 [Warning] WSREP: last seen seqno below limit for trx source: 9b6d3816-9c37-11e2-0800-a6e6b0729b93 version: 2 local: 1 state: CERTIFYING flags: 1 conn_id: 2214030 trx_id: 58980295 seqnos (l: 12538076, g: 12510994, s: 12510963, d: -1, ts: 1365509235123894000)
130409 8:07:15 [Warning] WSREP: last seen seqno below limit for trx source: 9b6d3816-9c37-11e2-0800-a6e6b0729b93 version: 2 local: 1 state: CERTIFYING flags: 1 conn_id: 2207815 trx_id: 58980355 seqnos (l: 12538077, g: 12510995, s: 12510974, d: -1, ts: 1365509235868810000)
130409 8:07:15 [Warning] WSREP: last seen seqno below limit for trx source: 9b6d3816-9c37-11e2-0800-a6e6b0729b93 version: 2 local: 1 state: CERTIFYING flags: 1 conn_id: 2214014 trx_id: 58980177 seqnos (l: 12538078, g: 12510996, s: 12510985, d: -1, ts: 1365509235870098000)
130409 8:07:15 [Warning] WSREP: last seen seqno below limit for trx source: 77b32202-9c3f-11e2-0800-4ddb5c914f02 version: 2 local: 0 state: CERTIFYING flags: 1 conn_id: 2204879 trx_id: 56810329 seqnos (l: 12538081, g: 12510999, s: 12510963, d: -1, ts: 1365509235111341000)
130409 8:07:15 [Warning] WSREP: last seen seqno below limit for trx source: 77b32202-9c3f-11e2-0800-4ddb5c914f02 version: 2 local: 0 state: CERTIFYING flags: 1 conn_id: 2204834 trx_id: 56810349 seqnos (l: 12538083, g: 12511001, s: 12510963, d: -1, ts: 1365509235216070000)
130409 8:07:15 [Warning] WSREP: last seen seqno below limit for trx source: 77b32202-9c3f-11e2-0800-4ddb5c914f02 version: 2 local: 0 state: CERTIFYING flags: 1 conn_id: 2205095 trx_id: 56810372 seqnos (l: 12538084, g: 12511002, s: 12510978, d: -1, ts: 1365509235870653000)
130409 8:07:21 [Note] WSREP: cleaning up ec4f0d2c-a0f1-11e2-0800-b39cacad59c1 (tcp://10.34.38.140:4567)
 len 224; hex a85432b5662b0000792f2fea652b000000fc0d8c622b000000000000000000000000000000000000000000000000000003000000000000000200000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000b1dbfe8c8d48a225000000000000000001000000000000008344510700000000deaf2f2c000000000200000000000000010000000000000000fc0d8c622b0000e2cd00000000000060e1117700000000020000000000000058471c60622b0000d8af2f2c000000001800000000000000; asc T2 f+ y// e+ b+ H % DQ /, b+ ` w XG `b+ /, ;
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 10.34.38.153 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
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:07:35 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 Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=193
max_threads=1250
thread_count=146
connection_count=146
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2837954 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2b62604aa460
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 2b66b20b10c8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c51e5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x69e894]
/lib64/libpthread.so.0[0x3ecb40eca0]
/lib64/libc.so.6(gsignal+0x35)[0x3eca4302c5]
/lib64/libc.so.6(abort+0x110)[0x3eca431d70]
/usr/sbin/mysqld[0x858dcc]
/usr/sbin/mysqld[0x8062a8]
/usr/sbin/mysqld[0x806bea]
/usr/sbin/mysqld[0x7d7b3d]
/usr/sbin/mysqld(_ZN30subselect_indexsubquery_engine4execEv+0x13d)[0x70bbed]
/usr/sbin/mysqld(_ZN14Item_subselect4execEv+0x4d)[0x70acbd]
/usr/sbin/mysqld(_ZN17Item_in_subselect8val_boolEv+0x20)[0x70b370]
/usr/sbin/mysqld(_ZN17Item_in_optimizer7val_intEv+0x152)[0x6c0552]
/usr/sbin/mysqld(_ZN4Item8val_boolEv+0xac)[0x6ab4bc]
/usr/sbin/mysqld(_ZN13Item_cond_and7val_intEv+0x3a)[0x6c17ca]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0xa80)[0x607bc0]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x25c7)[0x5941a7]
/usr/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x3b9)[0x5a6599]
/usr/sbin/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x7b)[0x5a9e7b]
/usr/sbin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x21e)[0x5aa4ae]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x174d)[0x59a02d]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x169)[0x59a799]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x15f)[0x6356df]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x6358a1]
/lib64/libpthread.so.0[0x3ecb40683d]
/lib64/libc.so.6(clone+0x6d)[0x3eca4d503d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2b62601341e0): is an invalid pointer
Connection ID (thread ID): 2214011
Status: KILL_QUERY

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

[Valerii Kravchuk (valerii-kravchuk)]

Please, check upstream http://bugs.mysql.com/bug.php?id=68051. Do you see any similarities to your use case?

What exact version of Percona Xtradb Cluster do you use?

[Raghavendra D Prabhu (raghavendra-prabhu)]

It was a MySQL / percona server bug, fixed in 5.5.31 - http://bugs.mysql.com/bug.php?id=68051

[Krunal Bauskar (krunal-bauskar)]

Upstream issue fixed. Issue is INVALID for PXC as it is not a PXC bug.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1135