Shutdown not communicating to workers
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
I have a interface.js which basically jsut setups to the kue dashboard.
I have a seperate js say worker.js
I send a code 15 (aka SIGTERM) via `kill -15 PID` to the interface.js PID which then issues the `queue.shutdown()` which I would of thought `signals all workers to stop processing after their current active job is done.` but by worker.js just continues to munch on the queue.
Is there something I'm missing in worker.js to tell interface.js it's a worker?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the interface.js shutdown path and the worker.js queue setup, then trace how queue.shutdown() is expected to communicate with workers after SIGTERM. Done means workers stop accepting new jobs while allowing their current active job to finish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100