Crash on Concurrent INSERT INTO .. ON DUPLICATE KEY UPDATE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
In Progress
|
Undecided
|
Seppo Jaakola |
Bug Description
After a node rejoins the cluster on SST, a potential crash can occur when the next writeset being executed involves a INSERT INTO ... ON DUPLICATE KEY UPDATE. In this case, we have db01, db02 and db03. db01 left the cluster for unknown issues, after rejoining the cluster thru xtrabackup sst, it crashed with the stack trace below. Then db02 followed, after bring db02 back online, db03 crashed as well.
130228 19:37:16 [ERROR] WSREP: FSM: no such a transition EXECUTING -> COMMITTED
00:37:16 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://
key_buffer_
read_buffer_
max_used_
max_threads=5000
thread_count=1469
connection_
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0xa859e260
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 = 7f6f68fc0e48 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f6ee507d620): is an invalid pointer
Connection ID (thread ID): 1710299
Status: NOT_KILLED
Full backtrace already shared with Seppo privately, let me know if anything else is needed.
Changed in percona-xtradb-cluster: | |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
may be a duplicate of: lp:1123233