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

Job being processed with older queue version #928

Closed
ilroux opened this issue Aug 6, 2016 · 4 comments
Closed

Job being processed with older queue version #928

ilroux opened this issue Aug 6, 2016 · 4 comments

Comments

@ilroux
Copy link

ilroux commented Aug 6, 2016

Hello folks:

I'm running into an issue where a sometimes a job is getting executed by an old version of the queue process block, when this happens is apparently random. I've read #391 and #403 the process block error handler for both versions looks like this:

queue.process('job', function (job, done) {
  var domain = require('domain').create();
  domain.on('error', function (err) {
    var err = `Unexpected error: ${err}`;
    log.error(err);
    done(err);
  });

  domain.run(function () {
    //Do some work
    done();
  });
});

To fixed i've tried the following:

  1. flushdb redis: No luck
  2. Check for other instances of the app: I've stopped the app and queue a couple of jobs so see if maybe another process was pinned and continue to execute the jobs, but was not the case, the queue remained the same until the app was turned on again.

I'm pretty lost at this point and I was hoping if you can point me in the right direction to understand what could be wrong?

Thank you for your time,
Juan

@ilroux
Copy link
Author

ilroux commented Aug 6, 2016

Fixed by changing the job name, closing the issue.

@ilroux ilroux closed this as completed Aug 6, 2016
@ryanvanderpol
Copy link

I'm experiencing the exact same thing and believe this should be reopened. I found this older issue (#494) where a few others seemed to have the same problem.

As stated here by @juankaram, changing the name of the job resolves the issue, but that is not a viable solution for me.

@ryanvanderpol
Copy link

To make things even more confusing, I actually REMOVED the job altogether. I completely deleted the job code from the app. But when I add a job to the queue with the same name as the old job it still executes the old job code.

@ryanvanderpol
Copy link

Bump. This is still a problem for me and I think this issue should be reopened.

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

No branches or pull requests

2 participants