RQG test engines/engine_stress.yy fails at /sql/filesort.cc:340 on ha_rows filesort

[joel9001]

Build: mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64

Test: engines/engine_stress.yy

During an RQG Test run of engines/engine_stress.yy against mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64, a crash occurs as shown below:

mysqld: /home/tokubuild/builds/build-tokudb-7.1.5-rc.4-debug-e/mysql-5.5.36/sql/filesort.cc:340: harows filesort(THD, TABLE_, SORTFIELD, uint, SQLSELECT, ha_rows, bool, ha_rows*): Assertion `thd->is_error() || kill_errno' failed. 23:05:23 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=1048576 read_buffer_size=131072 max_used_connections=55 max_threads=151 thread_count=55 connection_count=55 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60758 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f0715ee1000 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 = 7f0716607de8 thread_stack 0x40000 /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(my_print_stacktrace+0x2e)[0x7fdac5] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(handle_fatal_signal+0x2ee)[0x6d3296] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7f0721c8bbb0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0720ea5f77] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0720ea95e8] /lib/x86_64-linux-gnu/libc.so.6(+0x2fd43)[0x7f0720e9ed43] /lib/x86_64-linux-gnu/libc.so.6(+0x2fdf2)[0x7f0720e9edf2] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z8filesortP3THDP5TABLEP13st_sort_fieldjP10SQL_SELECTybPy+0x2387)[0x6d292e] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyy+0x7f4)[0x7b960f] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z21mysql_execute_commandP3THD+0x2404)[0x5bed21] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x157)[0x5c35eb] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xac2)[0x5c41ef] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z10do_commandP3THD+0x242)[0x5c57e8] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x107)[0x66d4fe] /mnt/ssd/mysql/mysql-5.5.36-tokudb-7.1.5-rc.4-debug-e-linux-x86_64/bin/mysqld(handle_one_connection+0x52)[0x66d5c4]

[joel9001]

This issue has been fixed in MySQL 5.6 and will be marked with the tokudb 7.1.6 milestone.

[joel9001]

This crash also occurs during the galera/galera_stress.yy test.

[prohaska]

see #28

[joel9001]

I have verfied this fix using the following build:

mysql-5.5.36-tokudb-1394550768-debug-e-linux-x86_64

Using the aforementioned build, I have re-run the engines/engine_stress.yy+zz and galera/galera_stress.yy+zz grammars individually 3 consecutive times using the RQG framework. On each occasion, the crash reported initially does not occur and the tests have returned the following result:

2014-03-12T09:52:05 Test completed successfully. 2014-03-12T09:52:05 gentest.pl exited with exit status STATUS_OK (0) 2014-03-12T09:52:05 [13101] ./runall.pl will exit with exit status STATUS_OK (0)

Marking this issue as closed.