[MDEV-23856] fts_optimize_wq accessed after shutdown of FTS Optimize thread Created: 2020-09-30  Updated: 2020-10-06  Resolved: 2020-09-30

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.28, 10.1.42, 10.3.19, 10.4.9, 10.5.0
Fix Version/s: 10.2.35, 10.3.26, 10.4.16, 10.5.7

Type: Bug Priority: Major
Reporter: Thirunarayanan Balathandayuthapani Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-20621 FULLTEXT INDEX activity causes InnoDB... Closed

 Description   

In fts_optimize_remove_table(), InnoDB tries to access the fts_optimize_wq
after shutdown the fts optimize thread. It affects debug build only

The following code fails:

        ut_d(mutex_enter(&fts_optimize_wq->mutex));
        ut_ad(!table->fts->in_queue);
        ut_d(mutex_exit(&fts_optimize_wq->mutex));

The issue was caused by the following commit:

commit a41d429765c7ddb528b9b438c68b25ff55d3bd55
Author: Thirunarayanan Balathandayuthapani <thiru@mariadb.com>
Date:   Tue Oct 22 12:05:42 2019 +0530
    MDEV-20621 FULLTEXT INDEX activity causes InnoDB hang


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