Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL)
-
bb-10.3-arm
Description
Result
CURRENT_TEST: innodb.innodb_bug14704286
|
mysqltest: At line 83: query 'reap' succeeded - should have failed with errno 1317...
|
 |
The result from queries just before the failure was:
|
< snip >
|
18 18 18 18
|
19 19 19 19
|
20 20 20 20
|
connection conn1;
|
select * from t1 force index(value) where value=12;
|
connection conn3;
|
Timeout in wait_condition.inc for select * from information_schema.processlist where state = 'Sending data' and
|
info = 'select * from t1 force index(value) where value=12'
|
Id User Host db Command Time State Info Progress
|
2 system user NULL Daemon NULL InnoDB purge worker NULL 0.000
|
3 system user NULL Daemon NULL InnoDB purge worker NULL 0.000
|
1 system user NULL Daemon NULL InnoDB purge coordinator NULL 0.000
|
4 system user NULL Daemon NULL InnoDB purge worker NULL 0.000
|
5 system user NULL Daemon NULL InnoDB shutdown handler NULL 0.000
|
16 root localhost test Sleep 31 NULL 0.000
|
17 root localhost test Sleep 30 NULL 0.000
|
18 root localhost test Sleep 30 NULL 0.000
|
19 root localhost test Query 0 Init show full processlist 0.000
|
kill query @id;
|
connection conn1;
|
Cause
Race condition: query may be already finished at the moment of kill.
Notes
There in mysql-test are about ~67 occurrences of ER_QUERY_INTERRUPTED, which are mostly correct as the queries are absolutely long or waiting on lock. Probably there are some incorrect ER_QUERY_INTERRUPTED queries of relatively short time.
Attachments
Issue Links
- blocks
-
MDEV-20301 InnoDB's MVCC has O(N^2) behaviors
- Closed