Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.2.12
Description
This issue seems to be similar to MDEV-12837 (which was closed) and I was asked to open a new case.
Just like it is described in the other defect, once the log shows these waits, everything is locked. It looks like it is triggered by a TRUNCATE TABLE:
_LOCK WAIT
MySQL thread id 138641, OS thread handle 139936878089984, query id 139638795 ........ Opening tables
TRUNCATE TABLE `ds$etl_dimension_discovery_local_standard_1`
2018-01-24 11:51:38 139938787669760 [Note] InnoDB: WSREP: BF lock wait long for trx:0x1a3598f query: TRUNCATE TABLE `ds$etl_dimension_discovery_local_standard_1`
TRANSACTION 27482511, ACTIVE 1997 sec_
An email with logs was sent out to Jan Lindström ...if need it I can send the link again.
Attachments
Issue Links
- duplicates
-
MDEV-15822 WSREP: BF lock wait long for trx
- Closed
- relates to
-
MDEV-12837 WSREP: BF lock wait long
- Closed
-
MDEV-13564 TRUNCATE TABLE and undo tablespace truncation are not compatible with Mariabackup
- Closed
-
MDEV-14637 Latching order violation during btr_cur_pessimistic_delete()
- Closed
-
MDEV-15855 Assertion `mysql_table' failed in innobase_get_computed_value upon DDL/DML on a table with virtual columns
- Closed