Shutdown not communicating to workers
See original GitHub issueI 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?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
The Right Way to Close an Operation
Communicate until it hurts. The shock of the initial announcement will prevent employees from absorbing everything you tell them at that time. After...
Read more >Guidance for Shutdown Furloughs - OPM
Employees who are neither excepted nor exempt and are scheduled for training during a shutdown furlough must be placed in a furlough status...
Read more >A Guide to Employee Rights When a Company Closes Down
Understanding your federal, state and contractual rights as an employee during a company shutdown can help you remain informed and prepared ...
Read more >How to Communicate with Someone ... - Develop Good Habits
If a co-worker has shut down on you, try communicating the mutual benefit of working together and effectively communicating.
Read more >Closing a Business - 7 Things to Communicate to Employees
But most importantly tell them why you feel certain information should be shared and why it is important to not share other information....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m having problems with shutdown as well. The example code from the readme does not seem to work. I will be in touch if i can find a solution.
I’m actually experiencing this problem when I call queue.shutdown myself. I’ve seen it work, but like other things in KUE it’s not consistent. Processors continue to consume the queue despite the shutdown being requested two days ago.