Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.2.28, 10.1.42, 10.3.19, 10.4.9, 10.5.0
-
Component/s: Storage Engine - InnoDB
-
Labels:None
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
|
Attachments
Issue Links
- is caused by
-
MDEV-20621 FULLTEXT INDEX activity causes InnoDB hang
-
- Closed
-