You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there.
I am just trying to integrate django-q in an existing django project.
The problem: Tasks are executed, but the cluster does not recognize when they are done.
Just print the word "async" leads to following log:
15:00:04 [Q] INFO Q Cluster stairway-cat-low-nevada starting.
15:00:07 [Q] INFO 17668 will use cpu [0]
15:00:07 [Q] INFO Process-1 guarding cluster stairway-cat-low-nevada
15:00:07 [Q] INFO Q Cluster stairway-cat-low-nevada running.
15:00:10 [Q] INFO Process-1:2 monitoring at 3172
15:00:10 [Q] INFO Process-1:3 pushing tasks at 19652
15:00:10 [Q] INFO Process-1:1 ready for work at 17668
15:00:10 [Q] INFO Process-1:1 processing [hotel-wolfram-mockingbird-louisiana]
async
So, the asyn task is executed, but there is no "Processed" logentry that will indicate, that the process has finished. Also are no hook called.
Is there any known problem with any configuration or module that can lead to this problem?
Edit:
I dived in a little bit deeper.
The task is in result_queue - but it seems the queue in cluster.monitor is not triggered.
The text was updated successfully, but these errors were encountered:
sparrow242
changed the title
Tasks are "processing" but hooks are not called and cluster recgonize they are finished and "processed"
Tasks are "processing" but hooks are not called and cluster don't recgonize they are finished and "processed"
Apr 26, 2021
Hi there.
I am just trying to integrate django-q in an existing django project.
The problem: Tasks are executed, but the cluster does not recognize when they are done.
Just print the word "async" leads to following log:
So, the asyn task is executed, but there is no "Processed" logentry that will indicate, that the process has finished. Also are no hook called.
Is there any known problem with any configuration or module that can lead to this problem?
Edit:
I dived in a little bit deeper.
The task is in result_queue - but it seems the queue in cluster.monitor is not triggered.
The text was updated successfully, but these errors were encountered: