Celery not picking CELERY_ALWAYS_EAGER settings

Question

I am running Django 1.8 + Celery 4.0.2 Celery is configured well and can run my Django tasks locally on redis backend. But when I try to use CELERY_ALWAYS_EAGER = True settings, this settings has no effect. Which is not the case with other settings, e.g. CELERY_TIMEZONE

Specifically, in pdb I see that app.conf.task_always_eager is False

lib/python2.7/site-packages/celery/app/task.py(520)apply_async() So somehow CELERY_ALWAYS_EAGER is not picked up and has no effect on app.conf.task_always_eager

More info from pdb:

> app.conf.get('CELERY_ALWAYS_EAGER')
> True
> app.conf.task_always_eager
> False

What can cause this? I know that Celery 4.x is in transition from old setting names to new ones, but they still promise old settings names still would be used as well.

have you placed from .celery import app as celery_app in your proj/proj/__init__.py? — John Moutafis
– John Moutafis, Commented May 12, 2017 at 9:03

Jamie Bull · Accepted Answer · 2018-06-13 14:47:54Z

67

CELERY_ALWAYS_EAGER has been renamed to CELERY_TASK_ALWAYS_EAGER in version 4.0+.

More accurately, all-caps settings have been deprecated in favor of directly configuring the celery app object, and several have been namespaced to either use task_ or worker_ as a prefix. Because there's still backwards-compatability with all-caps settings, this indirectly renamed the all-caps setting as well.

From the changelog:

The celery_ prefix has also been removed, and task related settings from this name-space is now prefixed by task_, worker related settings with worker_.

edited Jun 13, 2018 at 14:47

Jamie Bull

13.6k18 gold badges80 silver badges124 bronze badges

answered Jun 2, 2017 at 2:34

GDorn

8,8916 gold badges42 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Maninder Singh · Accepted Answer · 2017-05-12 09:06:03Z

-1

Please restart celery worker after setting CELERY_ALWAYS_EAGER = True in settings.py and see if it helps.

answered May 12, 2017 at 9:06

Maninder Singh

8491 gold badge7 silver badges13 bronze badges

4 Comments

AlexA Over a year ago

I am event not running a worker, I have Django runserver running (also, restarted) and expecting celery tasks to execute inside it.

Maninder Singh Over a year ago

Sorry, I did not get your point. How you are managing celery to up and running? are you managing it through supervisor? Did you run this command celery worker -A yourapp --loglevel=INFO to start celery or something else

AlexA Over a year ago

I managed to run celery worker -A yourapp --loglevel=INFO successfully and it's receieving tasks. Now I have a different goal: to help other developers run Django and tasks without celery, so that tasks are immediately executed inside Django process. For instance, this helps debugging tasks.

yrekkehs Over a year ago

Can confirm with CELERY_TASK_ALWAYS_EAGER = True in settings will run the tasks synchronously (so in multi-setting environments changing testing and local environments) one doesn't need to start up celery. This is helpful for team members who don't know celery and reduces overhead.

Collectives™ on Stack Overflow

Celery not picking CELERY_ALWAYS_EAGER settings

2 Answers 2

Comments

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related