[MDEV-23877] Document deprecation/removal of innodb_lock_schedule_algorithm Created: 2020-10-02  Updated: 2020-10-22  Resolved: 2020-10-05

Status: Closed
Project: MariaDB Server
Component/s: Documentation, Storage Engine - InnoDB
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Geoff Montee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16664 InnoDB: Failing assertion: !other_loc... Closed

 Description   

When MDEV-16664 is closed, we should document the deprecation/removal of innodb_lock_schedule_algorithm.

 Comments   
Comment by Marko Mäkelä [ 2020-10-05 ]

Due to the regression MDEV-16664 (potential corruption due to wrongly granting exclusive locks on the same record to more than one active transaction at a time), I did the following:

  1. Reverted the default back to the safe value
  2. Added a deprecation and corruption warning
  3. Removed the option innodb_lock_schedule_algorithm and related code (MariaDB Server 10.6) that had been added in MDEV-11039.
Comment by Geoff Montee (Inactive) [ 2020-10-05 ]

Documented here: https://mariadb.com/kb/en/innodb-system-variables/#innodb_lock_schedule_algorithm

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