Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6
Description
The function DeadlockChecker::check_and_resolve() is being executed while continuously holding lock_sys.mutex. Moving the deadlock detection to lock_wait() (which was refactored in MDEV-24671) will allow the check to release lock_sys.mutex between search iterations.
It may also be possible to avoid holding lock_sys.mutex altogether, and instead only use lock_sys.wait_mutex and various trx_t::mutex.
Attachments
Issue Links
- blocks
-
MDEV-24738 Improve the InnoDB deadlock checker
-
- Closed
-
- is part of
-
MDEV-20612 Improve InnoDB lock_sys scalability
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is part of |
Link |
This issue blocks |
Status | Open [ 1 ] | In Progress [ 3 ] |
issue.field.resolutiondate | 2021-02-04 15:56:25.0 | 2021-02-04 15:56:25.226 |
Fix Version/s | 10.6.0 [ 24431 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 118599 ] | MariaDB v4 [ 158831 ] |