Skip to content
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

Closed
bwang29 opened this issue Jan 24, 2015 · 4 comments
Closed

Precisely half of the jobs get processed. #503

bwang29 opened this issue Jan 24, 2015 · 4 comments
Labels

Comments

@bwang29
Copy link

bwang29 commented Jan 24, 2015

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?

@bwang29 bwang29 changed the title Precisely half ofthe jobs get processed. Precisely half of the jobs get processed. Jan 24, 2015
@behrad
Copy link
Collaborator

behrad commented Jan 25, 2015

There should be some error in your process callback which occasionally prevents done to be called, so job get's stuck in active. those stuck active jobs keep your concurrency bandwidth and process will not accept new jobs a bit later...

@micahlmartin
Copy link

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.

@behrad
Copy link
Collaborator

behrad commented Jan 29, 2015

this will seem a massive issue unless you are properly handling errors in your code @micahlmartin
You can use

  • domains
  • promises error handling
  • process uncaught error handlers

please read #391 and #403 or even #130 (comment)

@bwang29
Copy link
Author

bwang29 commented Jan 29, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants