You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2023/07/31 21:31:52 UTC

[GitHub] [airflow] potiuk commented on pull request #32983: doc: local executors - rephrase scheduler process

potiuk commented on PR #32983:
URL: https://github.com/apache/airflow/pull/32983#issuecomment-1659196139

   Well. Actualy the docs were right before. All executors - no matter if "remote" or "local" have an internal in-scheduler executor that runs as sub-process. For example this is what communicates and monitors running pods when Kubernetes Executor is used, and this is the process that sends Celery tasks and monitors for their status for CeleryExecutor. So executor process in-scheduler will run independently if it is "local" or "remote" executor.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org