raphaelauv commented on code in PR #41730:
URL: https://github.com/apache/airflow/pull/41730#discussion_r1732749122


##########
docs/apache-airflow/core-concepts/executor/index.rst:
##########
@@ -53,7 +53,7 @@ If you want to check which executor is currently set, you can 
use the ``airflow
 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 are two types of executors - those that run tasks *locally* (inside the 
``scheduler`` process), and those that run their tasks *distributed* (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 distributed executors for a multi-machine/cloud 
installation.

Review Comment:
   distributed -> externally 
   
   so we have locally and externally
   
   wdyt ?



-- 
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]

Reply via email to