[MDEV-27550] The test galera.MW-328D no longer reproduces a deadlock Created: 2022-01-20  Updated: 2023-11-27  Resolved: 2022-03-08

Status: Closed
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.5, 10.6, 10.7, 10.8
Fix Version/s: 10.5.16, 10.6.8, 10.7.4, 10.8.3

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Vladislav Lesin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-27025 insert-intention lock conflicts with ... Closed

 Description   

Ever since InnoDB stopped to flag some bogus record lock conflicts, the test galera.MW-328D started failing:

10.6 bd03c0e51629e1c3969a171137712a6bb854c232

 
CURRENT_TEST: galera.MW-328D
 
mysqltest: At line 37: query 'reap' succeeded - should have failed with error ER_LOCK_DEADLOCK (1213)...

10.5 be8113861c2d12bb0f7048523f886cab53326d8e

 
CURRENT_TEST: galera.MW-328D
 
mysqltest: At line 37: query 'reap' succeeded - should have failed with errno 1213...

This test will have to be adjusted so that it will reproduce a real locking conflict and deadlock, or it should be removed.

 Comments   
Comment by Vladislav Lesin [ 2022-01-20 ]

The reason of the the failure is the following. The transaction of connection node_1 acquires lock, then the transaction of node_1a creates conflicting waiting for node_1 lock, then node_1 transaction requests lock. Before MDEV-27025 fix the requested lock would conflict with the waiting lock of node_1a. After the fix, the lock is granted as node_1 already holds lock, and node_1a waiting for node_1.

Comment by Marko Mäkelä [ 2022-03-07 ]

Now that MDEV-27025 is being reverted due to the regression MDEV-27992, this test will start to work again.

Generated at Thu Feb 08 09:53:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.