[MDEV-29433] innodb.lock_delete_updated is unstable Created: 2022-09-01  Updated: 2022-09-13  Resolved: 2022-09-08

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Fix Version/s: 10.3.37, 10.4.27, 10.5.18, 10.6.10, 10.7.6, 10.8.5, 10.9.3, 10.10.2

Type: Task Priority: Major
Reporter: Vladislav Lesin Assignee: Vladislav Lesin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-27992 DELETE fails to delete record after b... Closed

 Description   

The test from MDEV-27992 is failing:

innodb.lock_delete_updated 'innodb'      w3 [ fail ]
 
        Test ended at 2022-08-31 13:50:52
 
 
 
CURRENT_TEST: innodb.lock_delete_updated
 
mysqltest: At line 26: query 'reap' succeeded - should have failed with error ER_LOCK_DEADLOCK (1213)...

Maybe we should use some syncpoint instead of include/wait_condition.inc, for example, lock_wait_suspend_thread_enter for 10.[345] and lock_wait_start for 10.6+, to make sure DELETE created waiting lock before the next UPDATE begins locking.
Generated at Thu Feb 08 10:08:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.