-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 10.2, 10.3, 10.1.41, 10.4
-
Component/s: Server, Storage Engine - InnoDB
-
Labels:None
-
Environment:Cloudlinux 7.7
Google Cloud Compute Engine
We are experiencing technical difficulties with the latest MariaDB 10.1.41-MariaDB.
This is only happening on one server while we have more with the same system package versions.
The database is freezing and does not accept new connections.
The error_log shows so much error data eg:
InnoDB: Warning: a long semaphore wait: |
--Thread 140300680931072 has waited at dict0dict.cc line 984 for 241.00 seconds the semaphore: |
Mutex at 0x7f9e26c112e8 '&dict_sys->mutex', lock var 1 |
Last time reserved by thread 140300697716480 in file not yet reserved line 0, waiters flag 1 |
InnoDB: Warning: semaphore wait:
|
--Thread 140300680931072 has waited at dict0dict.cc line 984 for 241.00 seconds the semaphore: |
Mutex at 0x7f9e26c112e8 '&dict_sys->mutex', lock var 1 |
Last time reserved by thread 140300697716480 in file not yet reserved line 0, waiters flag 1 |
We can provide more error log data but not in a public.
- causes
-
MDEV-20987 InnoDB fails to start when fts table has FK relation
-
- Closed
-
-
MDEV-23856 fts_optimize_wq accessed after shutdown of FTS Optimize thread
-
- Closed
-
- relates to
-
MDEV-19529 InnoDB hang on DROP FULLTEXT INDEX
-
- Closed
-