This is an automated email from the ASF dual-hosted git repository. potiuk pushed a commit to branch v2-0-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit aa50ae45fd92d0d5894be87591f333be43f39705 Author: Jon Quinn <[email protected]> AuthorDate: Tue Feb 23 13:31:38 2021 +0000 Fix grammar in production-deployment.rst (#14386) (cherry picked from commit 4fb943c21425f055e555a95ef9e4f7ba4690ee8b) --- docs/apache-airflow/production-deployment.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow/production-deployment.rst b/docs/apache-airflow/production-deployment.rst index 439afe1..042b655 100644 --- a/docs/apache-airflow/production-deployment.rst +++ b/docs/apache-airflow/production-deployment.rst @@ -56,9 +56,9 @@ Once that is done, you can run - Multi-Node Cluster ================== -Airflow uses :class:`~airflow.executors.sequential_executor.SequentialExecutor` by default. However, by it +Airflow uses :class:`~airflow.executors.sequential_executor.SequentialExecutor` by default. However, by its nature, the user is limited to executing at most one task at a time. ``Sequential Executor`` also pauses -the scheduler when it runs a task, hence not recommended in a production setup. You should use the +the scheduler when it runs a task, hence it is not recommended in a production setup. You should use the :class:`~airflow.executors.local_executor.LocalExecutor` for a single machine. For a multi-node setup, you should use the :doc:`Kubernetes executor <../executor/kubernetes>` or the :doc:`Celery executor <../executor/celery>`.
