-
Notifications
You must be signed in to change notification settings - Fork 867
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.
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
Precisely half of the jobs get processed. #503
Comments
There should be some error in your process callback which occasionally prevents |
IS there a solution to this? This is constantly happening to me where something is going wrong in the jobs and then they just sit their in an active state and no new jobs can be picked up. This seems like a massive issue. |
this will seem a massive issue unless you are properly handling errors in your code @micahlmartin
please read #391 and #403 or even #130 (comment) |
This issue can be closed now. It happened that we had another "left-over" server listening to the Kue and that server is running old, bad code. The kue accepts the jobs correctly. Apologize for not figuring out by ourselves. |
I'm using the latest kue in node.js. Right now precisely half of the jobs are picked up by polarr_jobs.process() although all request can be seen as active/completed in the Kue UI.
For example, the first time a job is submitted to kue, it shows up and stuck in Active
the second job is submitted to kue, it shows up in Active, then completed
the third job is submitted to kue, it shows up and stuck in Active
the forth job is submitted to kue, it shows up in Active, then completed
so on and so forth..
What might be the issue?
The text was updated successfully, but these errors were encountered: