[MDEV-31126] ER_FAILED_READ_FROM_PAR_FILE upon concurrent LOCK and CREATE Created: 2023-04-25  Updated: 2023-11-28

Status: Open
Project: MariaDB Server
Component/s: Locking, Partitioning
Affects Version/s: 10.6, 10.9, 10.10, 10.11, 11.0, 11.1
Fix Version/s: 10.6, 10.11, 11.0, 11.1

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Oleksandr Byelkin
Resolution: Unresolved Votes: 0
Labels: 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.
Generated at Thu Feb 08 10:21:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.