ALTER TABLE causes Failing assertion: trx_is_registered_for_2pc(trx)
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
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_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
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_
read_buffer_
max_used_
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_
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/
/run/shm/
/lib/x86_
/lib/x86_
/lib/x86_
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/lib/x86_
/lib/x86_
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://
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.
no longer affects: | codership-mysql/5.5 |
Fix committed in
lp:~codership/codership-mysql/5.5-23 r3926
lp:codership-mysql/5.5 r3895
lp:codership-mysql/5.6 r3964