[MDEV-25936] Crash during DDL that involves FULLTEXT INDEX Created: 2021-06-16  Updated: 2021-11-10  Resolved: 2021-06-16

Status: Closed
Project: MariaDB Server
Component/s: Full-text Search, Storage Engine - InnoDB
Affects Version/s: 10.6
Fix Version/s: 10.6.2

Type: Bug Priority: Blocker
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: crash, purge, race, regression-10.6

Issue Links:
Problem/Incident
causes MDEV-26274 On timeout, fts_lock_table() attempts... Closed
is caused by MDEV-25506 Atomic DDL: .frm file is removed and ... Closed
Relates
relates to MDEV-27017 Assertion failure 'table->get_ref_cou... Closed

 Description   

In a recent 10.6-based branch, the following was observed:

innodb.foreign_key 'innodb,read-ahead'   w2 [ fail ]
        Test ended at 2021-06-15 07:34:57
 
CURRENT_TEST: innodb.foreign_key
mysqltest: At line 165: query 'DROP DATABASE best' failed: <Unknown> (2013): Lost connection to server during query
2021-06-15 07:34:56 0xaf95eb40  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.6.2/storage/innobase/dict/dict0dict.cc line 1895
InnoDB: Failing assertion: table->get_ref_count() == 0

thiru was able to repeat this locally. The reason turned out to be a race condition in the fts_lock_table() check that tries to ensure that no purge task is executing on an internal FTS_ table.


Generated at Thu Feb 08 09:41:31 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.