Difference between revisions of "Airflow executors"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
# full import path to the class when using a custom executor. | # full import path to the class when using a custom executor. | ||
executor = SequentialExecutor | executor = SequentialExecutor | ||
+ | |||
+ | |||
+ | |||
+ | airflow celery worker | ||
+ | .../... | ||
+ | airflow command error: argument GROUP_OR_COMMAND: celery subcommand works only with CeleryExecutor, CeleryKubernetesExecutor and executors derived from them, your current executor: | ||
+ | SequentialExecutor, subclassed from: BaseExecutor, see help above. | ||
== Related == | == Related == |
Revision as of 11:01, 20 December 2022
airflow info | grep executor executor | SequentialExecutor
airflow.cfg # The executor class that airflow should use. Choices include # ``SequentialExecutor``, ``LocalExecutor``, ``CeleryExecutor``, ``DaskExecutor``, # ``KubernetesExecutor``, ``CeleryKubernetesExecutor`` or the # full import path to the class when using a custom executor. executor = SequentialExecutor
airflow celery worker .../... airflow command error: argument GROUP_OR_COMMAND: celery subcommand works only with CeleryExecutor, CeleryKubernetesExecutor and executors derived from them, your current executor: SequentialExecutor, subclassed from: BaseExecutor, see help above.
Related
See also
- Airflow executors:
LocalExecutor, CeleryExecutor, CeleryKubernetesExecutor, KubernetesExecutor
- Apache Airflow, Installation, configuration
airflow.cfg
, monitoring, Amazon Managed Workflows for Apache Airflow (MWAA),airflow
, Airflow Scheduler, providers, Workflows, Airflow executors, Airflow versions, Datadog integration
Advertising: