You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2021/08/02 13:44:15 UTC
[airflow] 20/22: Doc: Strip unnecessary arguments from MariaDB JIRA
URL (#17296)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v2-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit bb59cc5251f5c825ec3d3c1be6ba80a712d3b74f
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Wed Jul 28 21:26:24 2021 +0100
Doc: Strip unnecessary arguments from MariaDB JIRA URL (#17296)
This was included in https://github.com/apache/airflow/pull/17287 but we can strip other args
(cherry picked from commit 8e76f3ca50c736629f8ad3d3b7d4851fb4bd90e0)
---
docs/apache-airflow/concepts/scheduler.rst | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/docs/apache-airflow/concepts/scheduler.rst b/docs/apache-airflow/concepts/scheduler.rst
index 6ea5ff2..0a1079e 100644
--- a/docs/apache-airflow/concepts/scheduler.rst
+++ b/docs/apache-airflow/concepts/scheduler.rst
@@ -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>`_.
+ 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.