innodb_lock_schedule_algorithm

Overview

In 10.6 ES, 10.6 CS:

Not present

In 10.5 ES, 10.5 CS, 10.4 ES, 10.4 CS, 10.3 ES, 10.3 CS, 10.2 ES, 10.2 CS:

The algorithm Innodb uses for deciding which locks to grant next when a lock is released. Possible values are FCFS grant the locks in First-Come-First-Served order; VATS use the Variance-Aware-Transaction-Scheduling algorithm, which uses an Eldest-Transaction-First heuristic.

See also: System Variables for MariaDB Enterprise Server 10.6, in 10.6 CS, in 10.5 ES, in 10.5 CS, in 10.4 ES, in 10.4 CS, in 10.3 ES, in 10.3 CS, in 10.2 ES, and in 10.2 CS

DETAILS

PARAMETERS

Command-line

--innodb_lock_schedule_algorithm={fcfs|vats}

Configuration file

Supported

Dynamic

No

Scope

Global

Data Type

ENUM (fcfs, vats)

Default Value

fcfs

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Removed in MariaDB Enterprise Server 10.6.4-1.

10.6 Community

  • Removed in MariaDB Community Server 10.6.0.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

  • Dynamic changed in MariaDB Community Server 10.3.3 from Yes to No

  • Default value changed in MariaDB Community Server 10.3.9 from vats to fcfs

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Added in MariaDB Community Server 10.2.3.

  • Dynamic changed in MariaDB Community Server 10.2.12 from Yes to No

  • Default value changed in MariaDB Community Server 10.2.17 from vats to fcfs

EXTERNAL REFERENCES