Description:
090730 13:54:02 InnoDB: Assertion failure in thread 139973065423120 in file row/row0mysql.c line 1534
InnoDB: Failing assertion: index->type & DICT_CLUSTERED
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
090730 13:54:02 - 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.
key_buffer_size=402653184
read_buffer_size=2097152
max_used_connections=2
max_threads=151
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1013249 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x24945b40
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 = 0x7f4e04d7afe8 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x29) [0x90f799]
/usr/libexec/mysqld(handle_segfault+0x41c) [0x5f367c]
/lib64/libpthread.so.0 [0x349fc0ee90]
/lib64/libc.so.6(gsignal+0x35) [0x349f4332f5]
/lib64/libc.so.6(abort+0x180) [0x349f434b20]
/usr/libexec/mysqld(row_unlock_for_mysql+0x32f) [0x7fb2cf]
/usr/libexec/mysqld(row_search_for_mysql+0x1a1e) [0x80842e]
/usr/libexec/mysqld(ha_innobase::index_read(unsigned char*, unsigned char const*, unsigned int, ha_rkey_function)+0x18f) [0x78242f]
/usr/libexec/mysqld(handler::read_range_first(st_key_range const*, st_key_range const*, bool, bool)+0xbe) [0x6cbc4e]
/usr/libexec/mysqld(handler::read_multi_range_first(st_key_multi_range**, st_key_multi_range*, unsigned int, bool, st_handler_buffer*)+0xd1) [0x6cbd81]
/usr/libexec/mysqld(QUICK_RANGE_SELECT::get_next()+0x180) [0x6b3110]
/usr/libexec/mysqld [0x6c6e75]
/usr/libexec/mysqld(mysql_delete(THD*, TABLE_LIST*, Item*, st_sql_list*, unsigned long long, unsigned long long, bool)+0x861) [0x67e391]
/usr/libexec/mysqld(mysql_execute_command(THD*)+0x3681) [0x602ed1]
/usr/libexec/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x21c) [0x6050ac]
/usr/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xdea) [0x60632a]
/usr/libexec/mysqld(do_command(THD*)+0xea) [0x606c1a]
/usr/libexec/mysqld(handle_one_connection+0x21d) [0x5f9dad]
/lib64/libpthread.so.0 [0x349fc0686a]
/lib64/libc.so.6(clone+0x6d) [0x349f4de25d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7f4904005550 is an invalid pointer
thd->thread_id=4
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
How to repeat:
It is repeatable on my environment. I believe what is happening is the Persistant manager in tomcat is attempting to create the JDBCSessionStore table and that is when things go wonky. I also have master to master replciation setup.
