Skip to content

Clarify description of worker control config #29247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jedcunningham merged 1 commit into from
Jan 30, 2023
Merged

Clarify description of worker control config #29247

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions airflow/config_templates/config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1762,8 +1762,10 @@ celery:
worker_enable_remote_control:
description: |
Specify if remote control of the workers is enabled.
When using Amazon SQS as the broker, Celery creates lots of ``.*reply-celery-pidbox`` queues. You can
prevent this by setting this to false. However, with this disabled Flower won't work.
In some cases when the broker does not support remote control, Celery creates lots of
``.*reply-celery-pidbox`` queues. You can prevent this by setting this to false.
However, with this disabled Flower won't work.
https://docs.celeryq.dev/en/stable/getting-started/backends-and-brokers/index.html#broker-overview
version_added: 2.3.0
type: boolean
example: ~
Expand Down
6 changes: 4 additions & 2 deletions airflow/config_templates/default_airflow.cfg
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -896,8 +896,10 @@ worker_concurrency = 16
worker_prefetch_multiplier = 1

# Specify if remote control of the workers is enabled.
# When using Amazon SQS as the broker, Celery creates lots of ``.*reply-celery-pidbox`` queues. You can
# prevent this by setting this to false. However, with this disabled Flower won't work.
# In some cases when the broker does not support remote control, Celery creates lots of
# ``.*reply-celery-pidbox`` queues. You can prevent this by setting this to false.
# However, with this disabled Flower won't work.
# https://docs.celeryq.dev/en/stable/getting-started/backends-and-brokers/index.html#broker-overview
worker_enable_remote_control = true

# The Celery broker URL. Celery supports RabbitMQ, Redis and experimentally
Expand Down