Queue is running in an old code. even I have updated the code and restarted the qcluster

[Rajesh-Itilite]

Queue is running in an old code. even I have updated the code and restarted the qcluster. But some time it works properly in same machine

Issue 1: Running in old code In v2.1 of my code, I named the variable as resp. In v2.4 i have changed it as response. Totally I restarted more than 60 times it is sometimes running in old code

Issue 2: it is not going to any of the qcluster in the multiple machines.

Issue 3: some times it is showing an attribute error on qmodule

w�������builtinsAttributeErrorQmodule 'user_management.resources.controller' has no attribute 'export_all_users'R.

My config

Q_CLUSTER = { "name": "usm-xxxxx", "workers": 2, "orm": "default", # Use Django's ORM + database for broker "max_attempts": 2, "retry": 2, "cpu_affinity": 1 } machine is 4 core 16gb

[msabatier]

Hi,

For issue 1 how are you defining your tasks, with the function name or the function as an object (see https://django-q.readthedocs.io/en/latest/tasks.html) ? In the later case the definition of the function is queued with the task at the time the task is defined ! To update it the only solution is to delete the task and then recreate it.

For issues 2 and 3 I think more context is needed.

[ashleych]

I have a similar issue. It is defined as a function name, and yet old code seems to be getting picked up