Affects Version/s: None
Fix Version/s: None
**Reported in Launchpad by Ovais Tariq last update 12-02-2014 18:30:09
The Percona Server version is 5.5.33-31.1.
The server crashed while doing an UNDO of a long running UPDATE query that had modified thousands of rows. The assertion raised was as follows:
131110 14:09:59 InnoDB: Assertion failure in thread 16 in file sync0rw.c line 319
InnoDB: Failing assertion: lock->lock_word == X_LOCK_DECR
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: about forcing recovery.
14:09:59 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/
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10952556 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
/lib/amd64/libc.so.1'_lwp_kill+0xa [0xfffffd7fff2a473a] [Signal 6 (ABRT)]
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.html
and follow instructions on how to resolve the stack trace.
Resolved stack trace is much more helpful in diagnosing the
problem, so please do resolve it
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.
And the resolved stack trace is as follows:
af909b rw_lock_free_func + 411
b66110 dict_index_remove_from_cache + 288
b66230 dict_table_remove_from_cache + 112
b6655d dict_table_LRU_trim + 269
b666f9 dict_table_get_on_id + 393
bf863f row_undo_mod + 95
bf02b8 row_undo_step + 104
be5638 que_run_threads + 1400
b06a9b trx_rollback_or_clean_recovered + 1163
b070cf trx_rollback_or_clean_all_recovered + 63
This is how data dictionary has been limited:
innodb_dict_size_limit = 256M