Difference between revisions of "Airflow scheduler"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
== See also == | == See also == | ||
| + | * {{airflow dag}} | ||
* {{Airflow Scheduler}} | * {{Airflow Scheduler}} | ||
* {{airflow cmd}} | * {{airflow cmd}} | ||
| − | |||
[[Category:Airflow]] | [[Category:Airflow]] | ||
Revision as of 12:32, 30 November 2022
Starting the scheduler
Related
https://airflow.apache.org/docs/apache-airflow/stable/concepts/dagfile-processing.html The DagFileProcessorManager runs user codes. As a result, you can decide to run it as a standalone process in a different host than the scheduler process. If you decide to run it as a standalone process, you need to set this configuration: AIRFLOW__SCHEDULER__STANDALONE_DAG_PROCESSOR=True and run the airflow dag-processor CLI command, otherwise, starting the scheduler process (airflow scheduler) also starts the DagFileProcessorManager
See also
- Template:Airflow dag
- Airflow Scheduler,
airflow scheduler, airflow scheduler --daemon, --help, airflow-scheduler airflow [ info | celery | config | db upgrad | config list | db init | scheduler | webserver | users | dags | kubernetes | pools | roles | tasks | variables | cheat-sheet | kereberos | plugins | rotate-fernet-key | sync-perm ] airflow --help
Advertising:
