himanshuchawla0807-gif commented on code in PR #74913:
URL: https://github.com/apache/airflow/pull/74913#discussion_r4303434233
##########
chart/docs/customizing-workers.rst:
##########
@@ -32,6 +32,50 @@ For example, to set resources on workers for CeleryExecutor:
limits:
cpu: 1
+Separate Celery worker sets
+---------------------------
+
+Use ``workers.celery.sets`` to configure workers for different queues. Each set
+inherits ``workers.celery`` settings and can override them, including
+``extraVolumes`` and ``extraVolumeMounts``. For example, mount different
existing
+PersistentVolumeClaims for two worker sets:
+
+.. code-block:: yaml
+ :caption: values.yaml
+
+ executor: CeleryExecutor
+ workers:
+ celery:
+ enableDefault: false
+ sets:
+ - name: analytics
+ queue: analytics
+ extraVolumes:
+ - name: input-data
+ persistentVolumeClaim:
+ claimName: analytics-input
+ extraVolumeMounts:
+ - name: input-data
+ mountPath: /opt/airflow/input
+ readOnly: true
+ - name: research
+ queue: research
+ extraVolumes:
+ - name: input-data
+ persistentVolumeClaim:
+ claimName: research-input
+ extraVolumeMounts:
+ - name: input-data
+ mountPath: /opt/airflow/input
+ readOnly: true
+
+Create both PersistentVolumeClaims before deploying the chart, and route tasks
+to the corresponding queue. ``enableDefault: false`` disables the default
worker
+set, so this example creates only the ``analytics`` and ``research`` sets.
Review Comment:
Updated in c05e6f13fc. The example now keeps the default worker set enabled,
and the prose explains the default queue consumer and multi-node PVC access
modes for inherited replicas/autoscaling. I checked the revised example as
StatefulSets and Deployments, with three worker workloads in each case,
distinct PVCs and read-only mounts. Regular/manual static checks and the Breeze
chart documentation build pass.
---
Drafted-by: OpenAI Codex (no human review before posting)
--
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]
