Percona Server with XtraDB

Custom Percona Server 5.5.27 build crashes when compiled with MAX_INDEXES between 121-128 in config.h.cmake

Reported by Jaime Sicam on 2012-08-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server
Undecided
Sergei Glushchenko
5.1
Undecided
Sergei Glushchenko
5.5
Undecided
Sergei Glushchenko

Bug Description

On Percona Server 5.5.27:
Edit config.h.cmake and change "#define MAX_INDEXES 64" to "#define MAX_INDEXES 121"
Try compiling and running MySQL and it will crash

Error when starting MySQL:
02:33:53 UTC - mysqld got signal 11 ;
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/

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

Thread pointer: 0x2d8ad70
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 = 7f1b38111c28 thread_stack 0x40000
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(my_print_stacktrace+0x2e)[0x76976e]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(handle_fatal_signal+0x41a)[0x65dd7a]
/lib64/libpthread.so.0[0x3894e0f500]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x676)[0x55edc6]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1168)[0x56daf8]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x33b)[0x57102b]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld[0x5714c4]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(_Z19do_handle_bootstrapP3THD+0x164)[0x571784]
/home/mybuster/mysql-binaries/Percona-Server-5.5.27-rel28.0/5.5.27/bin/mysqld(handle_bootstrap+0x4a)[0x5717ea]
/lib64/libpthread.so.0[0x3894e07851]
/lib64/libc.so.6(clone+0x6d)[0x3894ae76dd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f1b2c0009c0): INSERT INTO tmp_db VALUES ('%','test','','Y','Y','Y','Y','Y','Y','N','Y','Y','Y','Y','Y','Y','Y','Y','N','N','Y','Y')
Connection ID (thread ID): 1
Status: NOT_KILLED

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.
error while creating grant tables
Installing MySQL system tables...

Installation of system tables failed! Examine the logs in
/home/mybuster/sandboxes/msb_5_5_27/data for more information.

Jaime Sicam (jssicam) on 2012-08-28
tags: added: i25814
tags: added: i25824
removed: i25814
Alexey Kopytov (akopytov) wrote :

See also http://bugs.mysql.com/bug.php?id=54127 (and http://bugs.mysql.com/bug.php?id=66560 is most likely a duplicate of that one). We have a fix for that bug in the rnt-5.1 branch: http://bazaar.launchpad.net/~percona-core/percona-server/rnt-5.1/revision/166

After applying patch http://bazaar.launchpad.net/~percona-core/percona-server/rnt-5.1/revision/166 following tests are failing:

main.create
main.ps_1general
main.ps_2myisam
main.ps_4heap
main.ps_5merge
main.ps_3innodb

They are designed with the assumption that MAX_INDEXES=64.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.