MySQL patches by Codership

ALTER TABLE causes Failing assertion: trx_is_registered_for_2pc(trx)

Bug #1237889 reported by Teemu Ollakka on 2013-10-10

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
MySQL patches by Codership	Status tracked in 5.6
5.5	Fix Released	Undecided	Unassigned	MySQL patches by Codership 5.5.34-25.9
5.6	Fix Released	Undecided	Unassigned	MySQL patches by Codership 5.6.14-25.1
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC	Status tracked in 5.6
5.5	Fix Released	Undecided	Unassigned	Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC 5.5.34-23.7.6
5.6	Fix Released	Undecided	Unassigned	Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC 5.6.14-25.1

Bug Description

ALTER TABLE statement caused the following:

2013-10-09 18:19:38 7fbb843f1700 InnoDB: Assertion failure in thread 140443354339072 in file ha_innodb.cc line 14438
InnoDB: Failing assertion: trx_is_registered_for_2pc(trx)
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:19:38 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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=15
max_threads=1024
thread_count=15
connection_count=15
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 415800 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2af2500
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 = 7fbb843f0e40 thread_stack 0x40000
/run/shm/galera/local1/mysql/sbin/mysqld(my_print_stacktrace+0x35)[0xa91222]
/run/shm/galera/local1/mysql/sbin/mysqld(handle_fatal_signal+0x3ae)[0x725af2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fbb9743ccb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7fbb96892425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7fbb96895b8b]
/run/shm/galera/local1/mysql/sbin/mysqld[0xabdeff]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z14ha_prepare_lowP3THDb+0xba)[0x63cc91]
/run/shm/galera/local1/mysql/sbin/mysqld(_ZN13MYSQL_BIN_LOG7prepareEP3THDb+0x42)[0xa24af4]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z15ha_commit_transP3THDbb+0x46f)[0x63b2a5]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x201)[0x89b5d6]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x8817)[0x7d77a4]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x40c)[0x7daa30]
/run/shm/galera/local1/mysql/sbin/mysqld[0x7da08c]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1082)[0x7ccbc1]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z10do_commandP3THD+0x639)[0x7cb6d6]
/run/shm/galera/local1/mysql/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1a5)[0x795292]
/run/shm/galera/local1/mysql/sbin/mysqld(handle_one_connection+0x33)[0x794ca4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7fbb97434e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbb9694fccd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fbb40004c90): ALTER TABLE comm00 ADD COLUMN (d DATETIME)
Connection ID (thread ID): 9
Status: 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.
Writing a core file

The reason for this is that wsrep hton is registered for ALTER even if it is running in TO isolation.