[MDEV-28517] Assertion failure in file fts0que.cc Created: 2022-05-09  Updated: 2022-08-04  Resolved: 2022-08-04

Status: Closed
Project: MariaDB Server
Component/s: Full-text Search, Storage Engine - InnoDB
Affects Version/s: 10.4.22
Fix Version/s: 10.3.36, 10.4.26, 10.5.17, 10.6.9

Type: Bug Priority: Major
Reporter: Heiki Laaniste Assignee: Thirunarayanan Balathandayuthapani
Resolution: Duplicate Votes: 1
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-27282 InnoDB: Assertion failure in file /lo... Closed

 Description   

2022-05-07 03:57:04 0x2b43349c0700 InnoDB: Assertion failure in file /local/p4clients/pkgbuild-URQZU/workspace/src/RDSMariaDB/storage/innobase/fts/fts0que.cc line 3831
InnoDB: Failing assertion: !query->intersection
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/innodb-recovery-modes/
InnoDB: about forcing recovery.
220507 3:57:04 [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.4.22-MariaDB-log
key_buffer_size=67108864
read_buffer_size=262144
max_used_connections=125
max_threads=258
thread_count=29
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 665959 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x2b434b9c8cc8
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 = 0x2b43349be5e8 thread_stack 0x40000
mysys/stacktrace.c:175(my_print_stacktrace)[0x5634cb3798b9]
sql/signal_handler.cc:219(handle_fatal_signal)[0x5634cadcfb70]
sigaction.c:0(__restore_rt)[0x2b29a7b64100]
/lib64/libc.so.6(gsignal+0x37)[0x2b29a7da65f7]
/lib64/libc.so.6(abort+0x148)[0x2b29a7da7ce8]
ut/ut0rbt.cc:469(rbt_eject_node)[0x5634cab2da36]
fts/fts0que.cc:4071(fts_query(trx_t*, dict_index_t*, unsigned int, unsigned char const*, unsigned long, fts_result_t**))[0x5634cb1d087e]
handler/ha_innodb.cc:9985(ha_innobase::ft_init_ext(unsigned int, unsigned int, String*))[0x5634cafb62e1]
sql/item_func.cc:6084(Item_func_match::init_search(THD*, bool))[0x5634cae34c47]
sql/sql_base.cc:9058(init_ftfuncs(THD*, st_select_lex*, bool))[0x5634cabaad0c]
sql/sql_select.cc:2861(JOIN::optimize_stage2())[0x5634cac4d65f]
sql/sql_select.cc:2342(JOIN::optimize_inner())[0x5634cac4ee37]
sql/sql_select.cc:1661(JOIN::optimize())[0x5634cac5149f]
sql/sql_select.cc:4741(mysql_select(THD*, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x5634cac51ec9]
sql/sql_select.cc:436(handle_select(THD*, LEX*, select_result*, unsigned long))[0x5634cac52924]
sql/sql_parse.cc:6570(execute_sqlcom_select)[0x5634cabf5f48]
sql/sql_parse.cc:6142(mysql_execute_command(THD*))[0x5634cabfdd1f]
sql/sql_parse.cc:8172(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x5634cac03c03]
sql/sql_parse.cc:1872(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x5634cac057eb]
sql/sql_parse.cc:1382(do_command(THD*))[0x5634cac0674d]
sql/sql_connect.cc:1464(do_handle_one_connection(CONNECT*))[0x5634cacd78e8]
sql/sql_connect.cc:1362(handle_one_connection)[0x5634cacd79e4]
perfschema/pfs.cc:1872(pfs_spawn_thread)[0x5634cb32ab1a]
/lib64/libpthread.so.0(+0x7dc5)[0x2b29a7b5cdc5]
/lib64/libc.so.6(clone+0x6d)[0x2b29a7e67c9d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2b434baa9060): SELECT
OP.idDat AS id,
OP.idDat AS customerID,
OP.displayed_name AS fullName,
OP.displayed_name AS companyName,
OP.type_id AS companyTypeID,
OP.firstname AS firstName,
OP.name AS lastName,
OP.optitle_id AS personTitleID,
OP.einvoice_id AS eInvoiceEmail,
OP.einvoice_reference AS eInvoiceReference,
OP.channel_email AS emailEnabled,
OP.channel_einvoice AS eInvoiceEnabled,
OP.mail_enabled AS mailEnabled,
OP.operator_id AS operatorIdentifier,
OP.edi_code AS EDI,
 
OP.clitype_id AS groupID,
OP.country_id AS countryID,
 
OP.orgper_idDat_payer AS payerID,
 
OP.phone AS phone,
OP.mobile AS mobile,
OP.mail AS email,
OP.fax AS fax,
OP.code AS code,
OP.regdate AS birthday,
OP.hansa_code AS integrationCode,
OP.starred AS flagStatus,
OP.color AS colorStatus,
OP.creditlimit AS credit,
OP.nosale AS salesBlocked,
OP.ref_no AS referenceNumber,
OP.customercard_code AS customerCardNumber,
OP.factoring_contract_number AS factoringContractNumber,
OP.not_european_union AS outsideEU,
OP.addedby, OP.vatrate_id_supplier AS homeStore FROM crmx_400.orgper AS OP WHERE OP.state = 1 AND OP.clitype_id > 0 AND OP.orgper_idDat_contact = 0 AND MATCH (OP.displayed_name, OP.phone, OP.mobile, OP.mail, OP.customercard_code,
OP.address_address, OP.address_address2, OP.address_postcode, OP.address_city,
OP.address_country, OP.address_state) AGAINST ('+\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\0* p[]*' IN BOOLEAN MODE) LIMIT 75
 
Connection ID (thread ID): 67012645
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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=off,condition_pushdown_from_having=on
 
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /rdsdbdata/db
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size unlimited unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 65535 65535 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 509814 509814 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: /rdsdbdata/tmp/core-%e-%p
 
2022-05-07 3:57:29 0 [Note] InnoDB: Using Linux native AIO
2022-05-07 3:57:29 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-05-07 3:57:29 0 [Note] InnoDB: Uses event mutexes
2022-05-07 3:57:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-07 3:57:29 0 [Note] InnoDB: Number of pools: 1
2022-05-07 3:57:29 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-05-07 3:57:29 0 [Note] InnoDB: Initializing buffer pool, total size = 93G, instances = 8, chunk size = 128M
2022-05-07 3:57:31 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-07 3:57:31 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-05-07 3:57:31 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=831745686276
2022-05-07 3:57:31 0 [Note] InnoDB: Transaction 100865696 was in the XA prepared state.
2022-05-07 3:57:31 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
2022-05-07 3:57:31 0 [Note] InnoDB: Trx id counter is 100865697
2022-05-07 3:57:31 0 [Note] InnoDB: Starting final batch to recover 3547 pages from redo log.
2022-05-07 3:57:33 0 [Note] InnoDB: Last binlog file '/rdsdbdata/log/binlog/mysql-bin-changelog.025318', position 1556080
2022-05-07 3:57:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-05-07 3:57:33 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
2022-05-07 3:57:33 0 [Note] InnoDB: Rollback of non-prepared transactions completed
2022-05-07 3:57:33 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-05-07 3:57:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-05-07 3:57:33 0 [Note] InnoDB: Setting file '/rdsdbdata/db/innodb/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-05-07 3:57:33 0 [Note] InnoDB: File '/rdsdbdata/db/innodb/ibtmp1' size is now 12 MB.
2022-05-07 3:57:33 0 [Note] InnoDB: Waiting for purge to start
2022-05-07 3:57:33 0 [Note] InnoDB: 10.4.22 started; log sequence number 831745698643; transaction id 100865698
2022-05-07 3:57:33 0 [Note] InnoDB: Loading buffer pool(s) from /rdsdbdata/db/innodb/ib_buffer_pool
220507 3:57:33 server_audit: MariaDB Audit Plugin version 1.4.13 STARTED.
220507 3:57:33 server_audit: logging started to the file /rdsdbdata/log/audit/server_audit.log.
2022-05-07 3:57:33 0 [Warning] /rdsdbbin/mysql/bin/mysqld: unknown variable 'loose-rocksdb_log_dir=/rdsdbdata/db/log'
2022-05-07 3:57:33 0 [Note] Recovering after a crash using /rdsdbdata/log/binlog/mysql-bin-changelog
2022-05-07 3:57:33 0 [Note] Starting crash recovery...
2022-05-07 3:57:33 0 [Note] InnoDB: Starting recovery for XA transactions...
2022-05-07 3:57:33 0 [Note] InnoDB: Transaction 100865696 in prepared state after recovery
2022-05-07 3:57:33 0 [Note] InnoDB: Transaction contains changes to 1 rows
2022-05-07 3:57:33 0 [Note] InnoDB: 1 transactions in prepared state after recovery
2022-05-07 3:57:33 0 [Note] Found 1 prepared transaction(s) in InnoDB
2022-05-07 3:57:33 0 [Note] Crash recovery finished.
2022-05-07 3:57:33 0 [Note] Server socket created on IP: '::'.
2022-05-07 3:57:33 0 [Note] InnoDB: Buffer pool(s) load completed at 220507 3:57:33
2022-05-07 3:57:33 0 [Warning] 'proxies_priv' entry '@% root@dev-dsk-hongxiny-2b-ce2f7f34.us-west-2.amazon.com' ignored in --skip-name-resolve mode.
2022-05-07 3:57:33 7 [Note] Event Scheduler: scheduler thread started with id 7
2022-05-07 3:57:33 0 [Note] Reading of all Master_info entries succeeded
2022-05-07 3:57:33 0 [Note] Added new Master_info '' to hash table
2022-05-07 3:57:33 0 [Note] /rdsdbbin/mysql/bin/mysqld: ready for connections.
Version: '10.4.22-MariaDB-log' socket: '/tmp/mysql.sock' port: 13336 Source distribution

Query crashes when killed. It was killed automatically by max_statement_time = 240s.
The orgper table contains around 18 mil rows. This part

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\0* p[]

was user input.


Generated at Thu Feb 08 10:01:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.