Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.6.9, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
-
None
-
Debian 10 amd64
Description
Mariadb crash after each below query:
INSERT INTO `b_user_index` (`USER_ID`, `NAME`, `SECOND_NAME`, `LAST_NAME`, `WORK_POSITION`, `UF_DEPARTMENT_NAME`, `SEARCH_USER_CONTENT`, `SEARCH_ADMIN_CONTENT`, `SEARCH_DEPARTMENT_CONTENT`) VALUES (7000, '', '', '', '', '', '7000', '7000 +7 (962) 981-7989 +7(962)981-7989 +79629817989 89629817989 79629817989 9629817989 629817989 29817989 9817989 817989 17989 7989 989 не выбрано 0', '') ON DUPLICATE KEY UPDATE `NAME` = '', `SECOND_NAME` = '', `LAST_NAME` = '', `WORK_POSITION` = '', `UF_DEPARTMENT_NAME` = '', `SEARCH_USER_CONTENT` = IF(SHA1(SEARCH_USER_CONTENT) = 'b7525fa5653c5b45f75d490825626e0880b394f4', SEARCH_USER_CONTENT, '7000'), `SEARCH_ADMIN_CONTENT` = IF(SHA1(SEARCH_ADMIN_CONTENT) = 'ac932ff7b355d03b541911c13e64c2c600fd009c', SEARCH_ADMIN_CONTENT, '7000 +7 (962) 981-7989 +7(962)981-7989 +79629817989 89629817989 79629817989 9629817989 629817989 29817989 9817989 817989 17989 7989 989 не выбрано 0'), `SEARCH_DEPARTMENT_CONTENT` = IF(SHA1(SEARCH_DEPARTMENT_CONTENT) = 'da39a3ee5e6b4b0d3255bfef95601890afd80709', SEARCH_DEPARTMENT_CONTENT, '')
|
The problem started after updating to 10.6.9.
error log:
2022-08-20 14:02:28 62242 [ERROR] InnoDB: (Duplicate key) writing word node to FTS auxiliary index table `z2s_db`.`b_user_index`
|
2022-08-20 14:02:28 0x7f0fec0d6700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.6.9/storage/innobase/que/que0que.cc line 728
|
InnoDB: Failing assertion: trx->error_state == DB_SUCCESS
|
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 mariadbd 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.
|
220820 14:02:28 [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.6.9-MariaDB-1:10.6.9+maria~deb10-log
|
key_buffer_size=8589934592
|
read_buffer_size=131072
|
max_used_connections=50
|
max_threads=2502
|
thread_count=50
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 19022199 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x7f0960000c18
|
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 = 0x7f0fec0d5d98 thread_stack 0x49000
|
??:0(my_print_stacktrace)[0x559ba9edfb0e]
|
??:0(handle_fatal_signal)[0x559ba99c5555]
|
??:0(__restore_rt)[0x7f120640d730]
|
??:0(gsignal)[0x7f1205f647bb]
|
??:0(abort)[0x7f1205f4f535]
|
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x559ba966b3d2]
|
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x559ba96571ca]
|
??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x559ba9e4ebb9]
|
??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x559ba9e3c3ff]
|
??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x559ba9e40ba1]
|
??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x559ba9e426de]
|
??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x559ba9e42945]
|
??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x559ba9e42ad5]
|
??:0(main)[0x559ba96cd5e8]
|
??:0(std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*))[0x559ba9d9565b]
|
??:0(std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*))[0x559ba9d9584f]
|
??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x559ba9c82958]
|
??:0(ha_check_and_coalesce_trx_read_only(THD*, Ha_trx_info*, bool))[0x559ba99c93a3]
|
??:0(ha_commit_trans(THD*, bool))[0x559ba99ca3b5]
|
??:0(trans_commit_stmt(THD*))[0x559ba98b5483]
|
??:0(mysql_execute_command(THD*, bool))[0x559ba97a985f]
|
??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x559ba979bf32]
|
??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x559ba97a6b3a]
|
??:0(do_command(THD*, bool))[0x559ba97a81f7]
|
??:0(do_handle_one_connection(CONNECT*, bool))[0x559ba98a5d17]
|
??:0(handle_one_connection)[0x559ba98a605d]
|
??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x559ba9be1b0e]
|
??:0(start_thread)[0x7f1206402fa3]
|
??:0(clone)[0x7f1206025eff]
|
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f0960010b50): INSERT INTO `b_user_index` (`USER_ID`, `NAME`, `SECOND_NAME`, `LAST_NAME`, `WORK_POSITION`, `UF_DEPARTMENT_NAME`, `SEARCH_USER_CONTENT`, `SEARCH_ADMIN_CONTENT`, `SEARCH_DEPARTMENT_CONTENT`) VALUES (7000, '', '', '', '', '', '7000', '7000 +7 (962) 981-7989 +7(962)981-7989 +79629817989 89629817989 79629817989 9629817989 629817989 29817989 9817989 817989 17989 7989 989 не выбрано 0', '') ON DUPLICATE KEY UPDATE `NAME` = '', `SECOND_NAME` = '', `LAST_NAME` = '', `WORK_POSITION` = '', `UF_DEPARTMENT_NAME` = '', `SEARCH_USER_CONTENT` = IF(SHA1(SEARCH_USER_CONTENT) = 'b7525fa5653c5b45f75d490825626e0880b394f4', SEARCH_USER_CONTENT, '7000'), `SEARCH_ADMIN_CONTENT` = IF(SHA1(SEARCH_ADMIN_CONTENT) = 'ac932ff7b355d03b541911c13e64c2c600fd009c', SEARCH_ADMIN_CONTENT, '7000 +7 (962) 981-7989 +7(962)981-7989 +79629817989 89629817989 79629817989 9629817989 629817989 29817989 9817989 817989 17989 7989 989 не выбрано 0'), `SEARCH_DEPARTMENT_CONTENT` = IF(SHA1(SEARCH_DEPARTMENT_CONTENT) = 'da39a3ee5e6b4b0d3255bfef95601890afd80709', SEARCH_DEPARTMENT_CONTENT, '')
|
|
|
Connection ID (thread ID): 62242
|
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=on,condition_pushdown_from_having=on,not_null_range_scan=off
|
|
|
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 /var/lib/mysql
|
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 8388608 unlimited bytes
|
Max core file size 0 unlimited bytes
|
Max resident set unlimited unlimited bytes
|
Max processes 255271 255271 processes
|
Max open files 1048576 1048576 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 255271 255271 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: core
|
|
|
Kernel version: Linux version 4.19.0-20-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.235-1 (2022-03-17)
|
|
|
2022-08-20 14:02:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
2022-08-20 14:02:35 0 [Note] InnoDB: Number of pools: 1
|
2022-08-20 14:02:35 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
|
2022-08-20 14:02:35 0 [Note] InnoDB: Using Linux native AIO
|
2022-08-20 14:02:35 0 [Note] InnoDB: Initializing buffer pool, total size = 17179869184, chunk size = 134217728
|
2022-08-20 14:02:35 0 [Note] InnoDB: Completed initialization of buffer pool
|
2022-08-20 14:02:35 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=744061940175,744061940175
|
2022-08-20 14:02:42 0 [Note] InnoDB: 2 transaction(s) which must be rolled back or cleaned up in total 104 row operations to undo
|
2022-08-20 14:02:42 0 [Note] InnoDB: Trx id counter is 2290494205
|
2022-08-20 14:02:42 0 [Note] InnoDB: Starting final batch to recover 63594 pages from redo log.
|
2022-08-20 14:02:44 0 [Note] InnoDB: 128 rollback segments are active.
|
2022-08-20 14:02:44 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
|
2022-08-20 14:02:44 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
|
2022-08-20 14:02:44 0 [Note] InnoDB: Creating shared tablespace for temporary tables
|
2022-08-20 14:02:44 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
|
2022-08-20 14:02:44 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
|
2022-08-20 14:02:44 0 [Note] InnoDB: Rolled back recovered transaction 2290494166
|
2022-08-20 14:02:44 0 [Note] InnoDB: 10.6.9 started; log sequence number 744761503269; transaction id 2290494207
|
2022-08-20 14:02:44 0 [Note] InnoDB: Rolled back recovered transaction 2290494173
|
2022-08-20 14:02:44 0 [Note] InnoDB: Rollback of non-prepared transactions completed
|
2022-08-20 14:02:44 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
|
2022-08-20 14:02:44 0 [Note] Plugin 'FEEDBACK' is disabled.
|
2022-08-20 14:02:44 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
|
2022-08-20 14:02:44 0 [Note] Server socket created on IP: '127.0.0.1'.
|
2022-08-20 14:02:44 0 [Note] /usr/sbin/mariadbd: ready for connections.
|
Version: '10.6.9-MariaDB-1:10.6.9+maria~deb10-log' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
|
2022-08-20 14:02:46 0 [Note] InnoDB: Buffer pool(s) load completed at 220820 14:02:46
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
Summary: if InnoDB table had a fulltext index and only one new row was inserted between the last sync (performed asynchronously by a dedicated thread) and server shutdown, the fulltext index wasn't properly updated and became out of sync with the data. Before 10.6.9 it was a silent error, in 10.6.9 an assertion crashed the server when detecting the inconsistency.
Is validation/fixing of the database / indices necessary?
If so, will the fixed version do this automatically or is manual intervention needed?
If manual work is needed, what are the steps to find and fix the inconsistencies?
ArthurBorsboom, this type of duplicate key error will lead to all FULLTEXT INDEX of the affected table to ‘freeze’, that is, no further updates to the indexes will be made, or the fulltext indexes will not reflect the latest changes to the table. That can be fixed by rebuilding the table (OPTIMIZE TABLE).
I am hereby confirming that upgrading mariadb from 10.9.2 > 10.9.3 solves the problem for me.
ArthurBorsboom, the fix of the duplicate key error has been merged up to 10.9, but as part of doing that, I forgot to apply some additional changes to 10.6 (see my previous comment). Those additional changes (which should prevent a crash if something else than what we fixed is causing the duplicate key error) have not been merged to 10.9 yet.
Please try the latest 10.9 branch. If it crashes, then
MDEV-15237was not fully fixed.