Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6, 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL)
-
None
Description
Note: The test case is non-deterministic, run with --repeat=N. It usually fails for me within 5-10 attempts, but it can vary on different machines and builds.
--source include/have_partition.inc
|
--source include/have_innodb.inc
|
|
|
CREATE TABLE t1 (a INT) ENGINE=InnoDB; |
ALTER TABLE t1 PARTITION BY KEY(a); |
CREATE TABLE t2 (b INT) ENGINE=InnoDB; |
|
|
--connect (con1,localhost,root,,test)
|
SET SESSION INNODB_LOCK_WAIT_TIMEOUT= 0; |
--send
|
CREATE OR REPLACE TABLE t1 (c INT) ENGINE=InnoDB; |
--connection default
|
ALTER TABLE t2 FORCE, ALGORITHM=COPY; |
LOCK TABLES t1 READ; |
|
|
# Cleanup
|
UNLOCK TABLES;
|
--connection con1
|
--reap
|
--disconnect con1
|
--connection default
|
DROP TABLE IF EXISTS t1, t2; |
|
10.6 8171f9da |
mysqltest: At line 14: query 'LOCK TABLES t1 READ' failed: ER_FAILED_READ_FROM_PAR_FILE (1696): Failed to read from the .par file |
Reproducible on 10.6-11.1.
Could not reproduce on 10.5.
On some reason, innodb_lock_wait_timeout appears to be important here, and not replaceable by lock_wait_timeout as would be expected for a DDL-only test case.