[MDEV-29566] Failed to read from the .par file upon concurrent DDL/SELECT with partition pruning - Jira

Details

Type: Bug
Status: Stalled (View Workflow)
Priority: Critical
Resolution: Unresolved
Affects Version/s: 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11
Fix Version/s: 10.6, 10.11
Component/s: Partitioning, Storage Engine - InnoDB
Labels:
- regression

Description

The test case is non-deterministic, run with --repeat=N. It fails for me (without rr) within a few attempts on various build types, but it can vary on different machines. The test is rr-able with --rr=-h, although it takes much longer, set repeat=N to a high value for rr.

--source include/have_innodb.inc

--source include/have_partition.inc

--connect (con1,localhost,root,,test)

CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=InnoDB PARTITION BY HASH (pk) PARTITIONS 4;

CREATE TABLE t2 (pk INT PRIMARY KEY) ENGINE=InnoDB;

SET SESSION INNODB_LOCK_WAIT_TIMEOUT= 0;

--send

  DROP TABLE t1;

--connection default

DROP TABLE t2;

--error 0,ER_NO_SUCH_TABLE

SELECT * FROM t1 PARTITION (p3);

# Cleanup

--connection con1

--reap

--disconnect con1

10.6 5e270ca2
mysqltest: At line 13: query 'SELECT * FROM t1 PARTITION (p3)' failed with wrong errno ER_FAILED_READ_FROM_PAR_FILE (1696): 'Failed to read from the .par file', instead of (0)...

The failure started happening (or, if it existed before, its probability hugely increased) after this commit in 10.6.8:

commit 8840583a92243f6ac543689148ca79c85fa0a09d

Author: Marko Mäkelä

Date:   Fri Mar 18 10:52:08 2022 +0200

    MDEV-27909 InnoDB: Failing assertion: state == TRX_STATE_NOT_STARTED ... on DDL

Attachments

Issue Links

relates to

MDEV-17567 Atomic DDL

Closed

MDEV-27180 Fully atomic partitioning DDL operations

In Review

MDEV-27618 Atomic DDL is not very atomic on partitioned tables

Confirmed

MDEV-30583 DB_DUPLICATE_KEY on CREATE OR REPLACE after ALTER TABLE change engine

Stalled

MDEV-35811 main.mysqldump-system fails with extra entries in innodb_index_stats

Open

MDEV-36352 main.partition_explicit_prune sporadically crashes on loong64

Open

(1 relates to)

Activity

Ascending order - Click to sort in descending order

Elena Stepanova created issue - 2022-09-18 16:52

Elena Stepanova made changes - 2022-09-18 16:53

Field	Original Value	New Value
Assignee		Marko Mäkelä [ marko ]

Elena Stepanova made changes - 2022-09-18 16:55

Summary

Failed to read from the .par file upon concurrent DDL/DML

Failed to read from the .par file upon concurrent DDL/SELECT

Elena Stepanova made changes - 2022-09-18 16:56

Summary

Failed to read from the .par file upon concurrent DDL/SELECT

Failed to read from the .par file upon concurrent DDL/SELECT with partition pruning

Elena Stepanova made changes - 2022-09-18 17:00

Description

_The test case is non-deterministic, run with \-\-repeat=N. It fails for me (without {{rr}} within a few attempts on various build types, but it can vary on different machines. The test is rr-able with {{\-\-rr=-h}}, although it takes much longer, set repeat=N to a high value for {{rr}}._

{code:sql}
--source include/have_innodb.inc
--source include/have_partition.inc

--connect (con1,localhost,root,,test)
CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=InnoDB PARTITION BY HASH (pk) PARTITIONS 4;
CREATE TABLE t2 (pk INT PRIMARY KEY) ENGINE=InnoDB;
SET SESSION INNODB_LOCK_WAIT_TIMEOUT= 0;
--send
DROP TABLE t1;
--connection default
DROP TABLE t2;
--error 0,ER_NO_SUCH_TABLE
SELECT * FROM t1 PARTITION (p3);

# Cleanup
--connection con1
--reap
--disconnect con1
{code}

{code:sql|title=10.6 5e270ca2}
mysqltest: At line 13: query 'SELECT * FROM t1 PARTITION (p3)' failed with wrong errno ER_FAILED_READ_FROM_PAR_FILE (1696): 'Failed to read from the .par file', instead of (0)...
{code}

The failure started happening (or, if it existed before, its probability hugely increased) after this commit in 10.6.8:
{noformat}
commit 8840583a92243f6ac543689148ca79c85fa0a09d
Author: Marko Mäkelä
Date: Fri Mar 18 10:52:08 2022 +0200

~~MDEV-27909~~ InnoDB: Failing assertion: state == TRX_STATE_NOT_STARTED ... on DDL
{noformat}

_The test case is non-deterministic, run with \-\-repeat=N. It fails for me (without {{rr}}) within a few attempts on various build types, but it can vary on different machines. The test is rr-able with {{\-\-rr=-h}}, although it takes much longer, set repeat=N to a high value for {{rr}}._

{code:sql}
--source include/have_innodb.inc
--source include/have_partition.inc

--connect (con1,localhost,root,,test)
CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=InnoDB PARTITION BY HASH (pk) PARTITIONS 4;
CREATE TABLE t2 (pk INT PRIMARY KEY) ENGINE=InnoDB;
SET SESSION INNODB_LOCK_WAIT_TIMEOUT= 0;
--send
DROP TABLE t1;
--connection default
DROP TABLE t2;
--error 0,ER_NO_SUCH_TABLE
SELECT * FROM t1 PARTITION (p3);

# Cleanup
--connection con1
--reap
--disconnect con1
{code}

{code:sql|title=10.6 5e270ca2}
mysqltest: At line 13: query 'SELECT * FROM t1 PARTITION (p3)' failed with wrong errno ER_FAILED_READ_FROM_PAR_FILE (1696): 'Failed to read from the .par file', instead of (0)...
{code}

The failure started happening (or, if it existed before, its probability hugely increased) after this commit in 10.6.8:
{noformat}
commit 8840583a92243f6ac543689148ca79c85fa0a09d
Author: Marko Mäkelä
Date: Fri Mar 18 10:52:08 2022 +0200

~~MDEV-27909~~ InnoDB: Failing assertion: state == TRX_STATE_NOT_STARTED ... on DDL
{noformat}

Marko Mäkelä made changes - 2022-09-19 09:05

Link

This issue relates to MDEV-27180 [ MDEV-27180 ]

Marko Mäkelä made changes - 2022-09-26 12:10

Status

Open [ 1 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2022-09-26 12:44

issue.field.resolutiondate

2022-09-26 12:44:01.0

2022-09-26 12:44:01.159

Marko Mäkelä made changes - 2022-09-26 12:44

Fix Version/s		10.6.11 [ 28441 ]
Fix Version/s		10.7.7 [ 28442 ]
Fix Version/s		10.8.6 [ 28443 ]
Fix Version/s		10.9.4 [ 28444 ]
Fix Version/s		10.10.2 [ 28410 ]
Fix Version/s	10.6 [ 24028 ]
Fix Version/s	10.7 [ 24805 ]
Fix Version/s	10.8 [ 26121 ]
Fix Version/s	10.9 [ 26905 ]
Fix Version/s	10.10 [ 27530 ]
Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Closed [ 6 ]

Marko Mäkelä made changes - 2022-09-27 07:58

Assignee	Marko Mäkelä [ marko ]	Michael Widenius [ monty ]
Resolution	Fixed [ 1 ]
Status	Closed [ 6 ]	Stalled [ 10000 ]

Marko Mäkelä made changes - 2022-09-27 07:59

Link

This issue relates to ~~MDEV-17567~~ [ ~~MDEV-17567~~ ]

Marko Mäkelä made changes - 2022-09-27 07:59

Fix Version/s		10.6 [ 24028 ]
Fix Version/s		10.7 [ 24805 ]
Fix Version/s		10.8 [ 26121 ]
Fix Version/s		10.9 [ 26905 ]
Fix Version/s		10.10 [ 27530 ]
Fix Version/s		10.11 [ 27614 ]
Fix Version/s	10.10.2 [ 28410 ]
Fix Version/s	10.6.11 [ 28441 ]
Fix Version/s	10.7.7 [ 28442 ]
Fix Version/s	10.8.6 [ 28443 ]
Fix Version/s	10.9.4 [ 28444 ]
Affects Version/s		10.11 [ 27614 ]
Priority	Major [ 3 ]	Critical [ 2 ]

Julien Fritsch made changes - 2023-03-03 17:29

Fix Version/s

10.7 [ 24805 ]

Julien Fritsch made changes - 2023-04-27 14:46

Fix Version/s

10.8 [ 26121 ]

Marko Mäkelä made changes - 2023-07-26 08:02

Link

This issue relates to MDEV-30583 [ MDEV-30583 ]

Julien Fritsch made changes - 2023-11-28 10:21

Fix Version/s

10.9 [ 26905 ]

Julien Fritsch made changes - 2023-11-28 10:31

Fix Version/s

10.10 [ 27530 ]

Marko Mäkelä made changes - 2024-04-11 08:18

Link

This issue relates to MDEV-27618 [ MDEV-27618 ]

Marko Mäkelä made changes - 2025-01-10 12:04

Link

This issue relates to MDEV-35811 [ MDEV-35811 ]

Marko Mäkelä made changes - 5 days ago

Link

This issue relates to MDEV-36352 [ MDEV-36352 ]

People

Assignee:: Michael Widenius

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2022-09-18 16:52

Updated:: 6 days ago 06:31

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration