Skip to content
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

Jump to bottom

Celery result backend not being correctly set #156

Closed
feliperuiz opened this issue Feb 8, 2018 · 1 comment
Closed

Celery result backend not being correctly set #156

feliperuiz opened this issue Feb 8, 2018 · 1 comment

Comments

@feliperuiz
Copy link

The configuration property celery_result_backend has been replaced by result_backend in apache/airflow@30076f1, which is supposed to be part of release 1.9.1. This project currently uses release 1.9.0, which uses the old property celery_result_backend. However, commit 7872cf1 updates the environment variable to set that property to the new name (and doesn't change the export bit, so that's a double woopsie).

I suggest reverting 7872cf1 to get it working again.
jenkins-attcomdev pushed a commit to att-comdev/shipyard that referenced this issue Feb 26, 2018
@eanylin
Update Airflow Celery 'result_backend'
656d277 
The current settings in Airflow is different from the recommended
one in [0]

This patch set is meant to align with the recommended configurations

Note also that due to issue reported in [1], we are keeping the
variable 'celery_result_backend' for now and will remove it when
we upgrade airflow to Airflow v1.9.1

[0] http://docs.celeryproject.org/en/latest/userguide/configuration.html
[1] puckel/docker-airflow#156

Change-Id: Ibead7c2ca76a984c09327579aedade036b959ab2
@puckel
Copy link
Owner

puckel commented Mar 1, 2018

Thanks. PR merged

@puckel puckel closed this as completed Mar 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@puckel @feliperuiz