You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Fokko Driesprong (JIRA)" <ji...@apache.org> on 2017/12/05 09:14:00 UTC
[jira] [Resolved] (AIRFLOW-966) Celery Broker Transport Options
[ https://issues.apache.org/jira/browse/AIRFLOW-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fokko Driesprong resolved AIRFLOW-966.
--------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.8.3)
(was: 1.9.0)
1.9.1
Issue resolved by pull request #2842
[https://github.com/apache/incubator-airflow/pull/2842]
> Celery Broker Transport Options
> -------------------------------
>
> Key: AIRFLOW-966
> URL: https://issues.apache.org/jira/browse/AIRFLOW-966
> Project: Apache Airflow
> Issue Type: Improvement
> Components: celery, executor
> Reporter: Desiree Cox
> Assignee: Desiree Cox
> Fix For: 1.9.1
>
>
> To use the CeleryExecutor with a Redis Sentinel broker, Celery must be provided with a dictionary of broker_transport_options with a key/value pair telling it the name of the desired redis service. There should be a broker_transport_options in the Celery section of airflow.cfg and CeleryExecutor should pass the options into the Celery worker configuration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)