Percona XtraDB Cluster 5.6 crashes on ALTER TABLE when sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
New
|
Undecided
|
Unassigned |
Bug Description
Percona XtraDB 5.6 crashes on ALTER table with VARCHAR field when sql_mode !=''. It's repeatable. Please help.
Stack:
Ubuntu 14.04.1 LTS
percona-
percona-toolkit 2.2.12
percona-xtrabackup 2.2.8-5059-1.trusty
percona-
percona-
percona-
percona-
Test case:
/*[19:27:58][ 0 ms]*/ Set character_
/*[19:27:58][ 16 ms]*/ Set character_
/*[19:27:58][ 0 ms]*/ Set character_
/*[19:27:58][ 0 ms]*/ set sql_mode=''
/*[19:29:13][ 0 ms]*/ set autocommit=1
/*[19:29:15][ 0 ms]*/ use `mydatabase`
/*[19:29:17][ 703 ms]*/ ALTER TABLE `mydatabase`
/*[19:29:19][ 516 ms]*/ ALTER TABLE `mydatabase`
/*[19:29:23][ 282 ms]*/ ALTER TABLE `mydatabase`
/*[19:29:30][ 0 ms]*/ UPDATE `mydatabase`
[..]
Bad (I run it from Sqlyog and galera node 1 terminated immediately):
/*[19:30:19][ 0 ms]*/ SET autocommit=0
/*[19:30:19][ 0 ms]*/ SELECT @@session.
/*[19:30:20][ 0 ms]*/ SET character_
/*[19:30:21][ 15 ms]*/ SET sql_mode=
/*[19:30:29][ 843 ms]*/ ALTER TABLE `mydatabase`
Error Code : 2013
Lost connection to MySQL server during query
(875 ms taken)
Error:
2015-01-29 09:09:45 5461 [ERROR] Transaction not registered for MySQL 2PC, but transaction is active
2015-01-29 09:09:45 7f20a485b700 InnoDB: Assertion failure in thread 139778175907584 in file row0mysql.cc line 4041
InnoDB: Failing assertion: table->n_rec_locks == 0
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.
09:09:45 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 XtraDB Cluster better by reporting any
bugs at https:/
key_buffer_
read_buffer_
max_used_
max_threads=202
thread_count=48
connection_count=46
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: 0x1ca6410
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 = 7f20a485ae20 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/lib/x86_
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f207002f3c0): is an invalid pointer
Connection ID (thread ID): 693168
Status: NOT_KILLED
find -type f | xargs grep ERROR | grep PC
./node1-
./node1-
./node1-
./node1-
./node1-
./node1-
@Thomas,
This has been fixed and pushed to PXC experimental repo. You can pull the package from there.