Skip to content

[v3-3-test] Update multi-node executor guidance (#48605) (#69154) #69388

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

Draft
github-actions wants to merge 1 commit into
base: v3-3-test
Choose a base branch
from
+7 −2
Draft

[v3-3-test] Update multi-node executor guidance (#48605) (#69154) #69388

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: 7 additions & 2 deletions airflow-core/docs/administration-and-deployment/production-deployment.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,13 @@ Multi-Node Cluster
==================

Airflow uses :class:`~airflow.executors.local_executor.LocalExecutor` by default. For a multi-node setup,
you should use the :doc:`Kubernetes executor <apache-airflow-providers-cncf-kubernetes:kubernetes_executor>` or
the :doc:`Celery executor <apache-airflow-providers-celery:celery_executor>`.
choose a remote executor, or a multi-executor configuration, that matches where tasks should run.
Common choices include the :doc:`Celery executor <apache-airflow-providers-celery:celery_executor>`,
the :doc:`Kubernetes executor <apache-airflow-providers-cncf-kubernetes:kubernetes_executor>`,
Amazon provider executors such as :doc:`Batch <apache-airflow-providers-amazon:executors/batch-executor>`
or :doc:`ECS <apache-airflow-providers-amazon:executors/ecs-executor>`, and the
:doc:`Edge executor <apache-airflow-providers-edge3:edge_executor>`. See the
:ref:`executor comparison <executor-types-comparison>` for the current list and trade-offs.


Once you have configured the executor, it is necessary to make sure that every node in the cluster contains
Expand Down