Assertion failure in thread in dict0dict.cc line 6322

Description

Version: '5.7.30-33-debug-log' socket: '/home/venki/work/ps/57/bld/mysql-test/var/tmp/mysqld.1.sock' port: 13001 Source distribution 2020-07-16 15:44:50 0x7f9cd500f700 InnoDB: Assertion failure in thread 140311565235968 in file dict0dict.cc line 6322 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.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 12:44:50 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. Please help us make Percona Server better by reporting any bugs at https://bugs.percona.com/key_buffer_size=1048576 read_buffer_size=131072 max_used_connections=1 max_threads=152 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61255 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x7f9c74000e10 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 = 7f9cd500edf8 thread_stack 0x40000 /home/venki/work/ps/57/bld/sql/mysqld(my_print_stacktrace+0x4b)[0x55ee178babc6] /home/venki/work/ps/57/bld/sql/mysqld(handle_fatal_signal+0x412)[0x55ee16df6e0b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7f9cda84e3c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f9cda34018b] /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f9cda31f859] /home/venki/work/ps/57/bld/sql/mysqld(+0x1c134c1)[0x55ee17c144c1] /home/venki/work/ps/57/bld/sql/mysqld(_Z32dict_table_check_for_dup_indexesPK12dict_table_t10check_name+0x10f)[0x55ee17cdb24c] /home/venki/work/ps/57/bld/sql/mysqld(_ZN11ha_innobase26commit_inplace_alter_tableEP5TABLEP18Alter_inplace_infob+0x1f9d)[0x55ee179f3f0f] /home/venki/work/ps/57/bld/sql/mysqld(_ZN7handler29ha_commit_inplace_alter_tableEP5TABLEP18Alter_inplace_infob+0xe7)[0x55ee16e9d457] /home/venki/work/ps/57/bld/sql/mysqld(+0x15e108a)[0x55ee175e208a] /home/venki/work/ps/57/bld/sql/mysqld(_Z17mysql_alter_tableP3THDPKcS2_P24st_ha_create_informationP10TABLE_LISTP10Alter_info+0x1e91)[0x55ee175e815d] /home/venki/work/ps/57/bld/sql/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x628)[0x55ee1776f858] /home/venki/work/ps/57/bld/sql/mysqld(_Z21mysql_execute_commandP3THDb+0x7276)[0x55ee17541cec] /home/venki/work/ps/57/bld/sql/mysqld(_Z11mysql_parseP3THDP12Parser_stateb+0x65b)[0x55ee17544037] /home/venki/work/ps/57/bld/sql/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xd0e)[0x55ee17538023] /home/venki/work/ps/57/bld/sql/mysqld(_Z10do_commandP3THD+0x5a6)[0x55ee17536da3] /home/venki/work/ps/57/bld/sql/mysqld(handle_connection+0x2b6)[0x55ee1768fa32] /home/venki/work/ps/57/bld/sql/mysqld(pfs_spawn_thread+0x174)[0x55ee178e1941] /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609)[0x7f9cda842609] /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f9cda41c103]Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f9c74005f10): ALTER TABLE t1 ADD FULLTEXT INDEX ft2 (f) Connection ID (thread ID): 2 Status: NOT_KILLED

Steps to reproduce:

CREATE TABLE t1 (f VARCHAR(256)) ENGINE=InnoDB; SET SESSION FOREIGN_KEY_CHECKS = OFF; ALTER TABLE t1 ADD FOREIGN KEY (f) REFERENCES non_existing_table (x); SET SESSION FOREIGN_KEY_CHECKS = ON; ALTER TABLE t1 ADD FULLTEXT INDEX ft1 (f); ALTER TABLE t1 ADD FULLTEXT INDEX ft2 (f); DROP TABLE t1;

Suggested fix:

Evaluate the fix for https://jira.mariadb.org/browse/MDEV-18016

Check https://github.com/MariaDB/server/commit/1522ee2949ae304ad90928

Environment

None

Smart Checklist

Activity

Show:

Julia Vural March 4, 2025 at 9:10 PM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

Won't Do

Details

Assignee

Reporter

Labels

Affects versions

Priority

Smart Checklist

Created July 16, 2020 at 1:18 PM
Updated March 4, 2025 at 9:10 PM
Resolved March 4, 2025 at 9:10 PM

Flag notifications