[MDEV-6614] Merge InnoDB: fix index->lock contention from MySQL 5.7 Created: 2014-08-20  Updated: 2017-02-20  Resolved: 2016-09-21

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.2.2

Type: Task Priority: Major
Reporter: Jan Lindström (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 1
Labels: innodb, xtradb

Issue Links:
PartOf
is part of MDEV-6113 merge 5.7 innodb Closed
Problem/Incident
causes MDEV-11336 Enable defragmentation on 10.2 when t... Closed

 Description   

revno: 6232 
revno: 6233
revno: 6902
  - WL#6326 : InnoDB: fix index->lock contention

The acquisition of node pointer page latches is protected by index->lock latch.Currently, index->lock protected all node pointer pages either in S or X mode, and no individual block->lock were acquired on node pointer pages. With this fix, node pointer pages are protected by individual block->lock, S-latch or X-latch. The acquisition of node pointer page latches is covered by index->lock, for preventing deadlocks.

InnoDB internally uses rw-lock implementation to keep consistency of internal
resources. Basically the rw-lock has 2 types S-lock (shared) and X-lock (exluded).
The fix adds the new type SX-lock (shared excluded) for room to optimize
concurrency and improve scalability more.

At least, S-lock and X-lock behave same, and compatible for current code. So,
nothing changed by only this fix as it is. (no functional/performance changes
for users)

The new state SX-lock will be used by the future work. (e.g. WL#6326: InnoDB:
fix index->lock contention)

  new state of rw_lock: SX-lock
        | S|SX| X|
      --+--+--+--+
       S| o| o| x|
      --+--+--+--+
      SX| o| x| x|
      --+--+--+--+
       X| x| x| x|
      --+--+--+--+
  


Generated at Thu Feb 08 07:13:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.