Skip to content

Update warning about MariaDB and multiple schedulers #17287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 1 commit into from
Jul 28, 2021
Merged

Update warning about MariaDB and multiple schedulers #17287

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/apache-airflow/concepts/scheduler.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,13 +123,14 @@ The following databases are fully supported and provide an "optimal" experience:

.. warning::

MariaDB does not implement the ``SKIP LOCKED`` or ``NOWAIT`` SQL clauses (see `MDEV-13115
<https://jira.mariadb.org/browse/MDEV-13115>`_). Without these features running multiple schedulers is not
supported and deadlock errors have been reported.
MariaDB did not implement the ``SKIP LOCKED`` or ``NOWAIT`` SQL clauses until version
`10.6.0 <https://jira.mariadb.org/browse/MDEV-25433?jql=project%20%3D%20MDEV%20AND%20fixVersion%20%3D%2010.6.0>`_.
Without these features, running multiple schedulers is not supported and deadlock errors have been reported. MariaDB
10.6.0 and following may work appropriately with multiple schedulers, but this has not been tested.

.. warning::

MySQL 5.x also does not support ``SKIP LOCKED`` or ``NOWAIT``, and additionally is more prone to deciding
MySQL 5.x does not support ``SKIP LOCKED`` or ``NOWAIT``, and additionally is more prone to deciding
queries are deadlocked, so running with more than a single scheduler on MySQL 5.x is not supported or
recommended.

Expand Down