[MDEV-17102] Server crash with failing assertion: index->table->stat_initialized Created: 2018-08-30  Updated: 2019-10-07  Resolved: 2019-10-07

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.14, 10.2.16
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Marko Mäkelä
Resolution: Incomplete Votes: 1
Labels: need_feedback

Issue Links:
Relates
relates to MDEV-6424 MariaDB server crashes with assertion... Closed

 Description   

A user saw the following crash:

2018-08-28 16:52:10 0x7efdeab32700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.16/storage/innobase/handler/ha_innodb.cc line 14096
InnoDB: Failing assertion: index->table->stat_initialized
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
InnoDB: about forcing recovery.
180828 16:52:10 [ERROR] 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.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
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.
 
Server version: 10.2.16-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=501
max_threads=502
thread_count=197
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1234125 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7efe180de8c8
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 = 0x7efdeab31d30 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56318186a0be]
/usr/sbin/mysqld(handle_fatal_signal+0x355)[0x5631812f5955]
sigaction.c:0(__restore_rt)[0x7efe980bd6d0]
/lib64/libc.so.6(gsignal+0x37)[0x7efe96391277]
:0(__GI_raise)[0x7efe96392968]
/usr/sbin/mysqld(+0x42a9ec)[0x5631810ac9ec]
ut/ut0rbt.cc:221(rbt_tree_add_child(ib_rbt_t const*, ib_rbt_bound_t*, ib_rbt_node_t*) [clone .isra.4] [clone .part.5])[0x5631814e2088]
handler/ha_innodb.cc:14321(ha_innobase::info_low(unsigned int, bool))[0x5631814e5545]
sql/handler.cc:2501(handler::ha_open(TABLE*, char const*, int, unsigned int))[0x5631812f9e73]
sql/table.cc:3335(open_table_from_share(THD*, TABLE_SHARE*, char const*, unsigned int, unsigned int, unsigned int, TABLE*, bool))[0x56318120e6cd]
sql/sql_base.cc:1890(open_table(THD*, TABLE_LIST*, Open_table_context*))[0x56318111d6f2]
sql/sql_base.cc:3433(open_and_process_table)[0x563181120741]
sql/sql_base.cc:4706(open_and_lock_tables(THD*, DDL_options_st const&, TABLE_LIST*, bool, unsigned int, Prelocking_strategy*))[0x563181120ac4]
sql/sql_parse.cc:6395(execute_sqlcom_select(THD*, TABLE_LIST*))[0x56318109bcd3]
sql/sql_parse.cc:3481(mysql_execute_command(THD*))[0x563181163f25]
sql/sql_parse.cc:8000(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x56318116af3e]
sql/sql_parse.cc:1821(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x56318116dfd5]
sql/sql_parse.cc:1377(do_command(THD*))[0x56318116ec05]
sql/sql_connect.cc:1335(do_handle_one_connection(CONNECT*))[0x5631812334ba]
sql/sql_connect.cc:1243(handle_one_connection)[0x5631812335dd]
pthread_create.c:0(start_thread)[0x7efe980b5e25]
/lib64/libc.so.6(clone+0x6d)[0x7efe96459bad]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7efe18087ce0): SELECT MIN(ID) FROM tab WHERE VID = 'somestr'
Connection ID (thread ID): 21154
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on

The table has the following definition:

CREATE TABLE `tab` (
  `VID` varchar(750) COLLATE utf8_unicode_ci NOT NULL,
  `ID` bigint(20) NOT NULL,
  PRIMARY KEY (`VID`(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci

This crash looks similar to MDEV-6424, but that bug has been fixed and the fix for that bug supposedly added a new warning that would give more details about the problem. In this case, the error log did not contain that warning.



 Comments   
Comment by Elena Stepanova [ 2018-08-30 ]

Please paste or attach the config file(s).

Comment by Elena Stepanova [ 2018-09-04 ]

And he said that he added the following options to tune the settings after the crash

Did it help?
And is there anything in /etc/my.cnf.d/ ?

Comment by Geoff Montee (Inactive) [ 2018-09-04 ]

Did it help?

He hasn't reported anymore crashes. He ran the original query a couple times and it did not crash, but I don't know if that's because the configuration changes helped or because the crash only happens when the query is run in certain scenarios. Would you like me to ask him to revert the changes and run the original query again?

And is there anything in /etc/my.cnf.d/

Only the default server.cnf, client.cnf, and enable_encryption.preset, but none of the files actually set any options.

Generated at Thu Feb 08 08:33:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.