Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2, 10.2.7, 10.2(EOL)
-
None
-
linux
Description
Running DELETE on a table with a single ROW which causes a cascade constraint to trigger hangs for long time (about 20 minutes in the reported case) and then crashes the instance with:
InnoDB: ###### Diagnostic info printed to the standard error stream
2017-08-10 19:08:35 140481422710528 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server becau
se it appears to be hung.
170810 19:08:35 [ERROR] mysqld got signal 6 ;
To reproduce:
1) Import attached dump
2) Execute:
DELETE FROM BRc273a13dfda91b1add89;
3) Wait ~20 minutes
On 10.1 the same completes successfully in 15 seconds.
Attachments
Issue Links
- blocks
-
MDEV-13678 DELETE with CASCADE takes a long time when Galera is enabled
- Closed
- relates to
-
MDEV-13246 Stale rows despite ON DELETE CASCADE constraint
- Closed
-
MDEV-15611 Due to the failure of foreign key detection, Galera slave node killed himself.
- Closed