innodb_lock_schedule_algorithm

In 10.6 ES:

Not present

In 10.5 ES, 10.4 ES:

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.5 ES, and in 10.4 ES

DETAILS

PARAMETERS

Dynamic

No

Scope

Global

Data Type

ENUM (fcfs, vats)

Default Value

fcfs

SKYSQL

Cloud

SkySQL Topology

ES Ver

Default

AWS

HA (Primary/Replica)

10.4

fcfs

AWS

HA (Primary/Replica)

10.5

fcfs

AWS

Transactional Standalone

10.4

fcfs

AWS

Transactional Standalone

10.5

fcfs

AWS

Distributed Transactions

10.5

Not present

GCP

ColumnStore

10.5

fcfs

GCP

ColumnStore Multi

10.5

fcfs

GCP

Galera

10.4

fcfs

GCP

Galera

10.5

fcfs

GCP

HA (Primary/Replica)

10.4

fcfs

GCP

HA (Primary/Replica)

10.5

fcfs

GCP

HTAP

10.5

fcfs

GCP

Transactional Standalone

10.4

fcfs

GCP

Transactional Standalone

10.5

fcfs

GCP

Distributed Transactions

10.5

Not present

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Removed in MariaDB Enterprise Server 10.6.4-1.

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

EXTERNAL REFERENCES