AMQP result backend is scheduled for deprecation

[Ben Earner]

For celery v.4.0.2 Using the current settings.py I get the following warning:

The AMQP result backend is scheduled for deprecation in  version 4.0 and removal in version v5.0.  Please use RPC backend or a persistent backend.

Can it simply be changed to this in settings.py?

CELERY_RESULT_BACKEND = 'rpc://'

Or does the broker url need changing as well? I'm still a bit clueless over some of the celery functionality and what this means for OpenREM...(!)

[Ed McDonagh]

Adding to future as not required for version 0.8.

As to what the necessary change is, I'd have to look into it. Happy for others to try, test and propose changes :-)

[David Platten]

I've been using the rpc celery backend on my live system for some time. It doesn't seem to have caused any problems (that I'm aware of...)

CELERY_RESULT_BACKEND = 'rpc'

[David Platten]

Apparently the rpc backend is much faster than ampq - see this post:

https://github.com/celery/celery/issues/1869

[Ed McDonagh]

We should do this for 0.8.0. Thanks @bearner.

[Ed McDonagh]

Changed celery results backend to rpc. Refs #582. Added -Ofair to linux celery command. Added note about versions of Celery on Windows. Refs #455, #541. [skip ci]

→ <<cset facda714c3b1>>

[Ed McDonagh]

Updated ref #582 in changes plus incidental white space removal. [skip ci]

→ <<cset 01c377b5badf>>

[Ed McDonagh]

Merged issue582celerybackend into develop.

Fixes #582

[skip ci]

→ <<cset 043b879f1cfa>>