Automattic / Automattic/kue

Error: Shutdown already in progress - critical issues with Kue

Open
#1,219 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
9.4k
Forks
858
PR merge metrics
No merged PRs in 30d

Description

Seems calling `queue.shutdown() `when more that one queue exists causes an error:

`Error: Shutdown already in progress`

See example below:

```
process.stdin.resume();

const kue = require('kue');

let queue = kue.createQueue({
redis: 'redis://localhost:6380'
});

queue.process('my-event', (job, done) => {
console.info(job.data);

done();
});

//_________________________________________________________________________________________________

let queue2 = kue.createQueue({
redis: 'redis://localhost:6380'
});

queue2.process('my-other-event', (job, done) => {
console.info(job.data);

done();
});

//_________________________________________________________________________________________________

let job = queue
.create('my-event', {foo: 'bar'})
.removeOnComplete(true)
.save();

setTimeout(() => {
queue.shutdown(0, (err) => {
if (err) {
return console.error(err);
}

console.info('queue shutdown');
});

}, 5000);

let job2 = queue2
.create('my-other-event', {foo: 'bar'})
.removeOnComplete(true)
.save();

setTimeout(() => {
queue2.shutdown(0, (err) => {
if (err) {
return console.error(err);
}

console.info('queue2 shutdown');
});

}, 5000);

```
While I am grateful for OS contribution, there is so much critical stuff that in undocumented in this project

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue provides no file or test names. Start by running the supplied two-queue Node.js/Redis reproduction and trace queue.shutdown(0) for both queue instances; done means each callback completes without “Shutdown already in progress” while both workers stop cleanly.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, redis
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.