amoghrajesh commented on code in PR #48528:
URL: https://github.com/apache/airflow/pull/48528#discussion_r2021365816
##########
airflow-core/docs/core-concepts/executor/index.rst:
##########
@@ -46,14 +46,17 @@ If you want to check which executor is currently set, you
can use the ``airflow
.. code-block:: bash
$ airflow config get-value core executor
- SequentialExecutor
+ LocalExecutor
Executor Types
--------------
-There are two types of executors - those that run tasks *locally* (inside the
``scheduler`` process), and those that run their tasks *remotely* (usually via
a pool of *workers*). Airflow comes configured with the ``SequentialExecutor``
by default, which is a local executor, and the simplest option for execution.
However, the ``SequentialExecutor`` is not suitable for production since it
does not allow for parallel task running and due to that, some Airflow features
(e.g. running sensors) will not work properly. You should instead use the
``LocalExecutor`` for small, single-machine production installations, or one of
the remote executors for a multi-machine/cloud installation.
+There is only one type of executor that runs tasks *locally* (inside the
``scheduler`` process),
+and those that run their tasks *remotely* (usually via a pool of *workers*).
Airflow comes configured with the ``LocalExecutor`` by default, which is a
local executor, and the simplest option for execution.
+However, the ``LocalExecutor`` is not advised for production use since it runs
processes in the scheduler process and that can have an impact on the
performance of the scheduler. You can use the ``LocalExecutor``
+for small, single-machine production installations, or one of the remote
executors for a multi-machine/cloud installation.
Review Comment:
Yeah more accurate!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
