Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The DynamicThreadPool does not seem to revive new workers after they are killed
See original GitHub issueWe currently used DynamicThreadPool with min: 2, max: 8 workers.
The workers start with 2 worker and after we used several workers, they scale up to 8 as expected. (maxInactiveTime)
After 60 seconds of idle-time, they scale down and the exit-handler is fired. (worker.on('exit', ...)
But if we then request some new workers after they were killed, it seems they don’t scale up to 8 again 🤔
We started to modified the code in node_modules and tried to just remove worker from this.workers, but it seems that this wasn’t enough to let it know to respawn new workers after they were killed
The worker.on('online', ... event wasn’t fired again after the 8 workers scaled down to 2 and expected to re-scale up
I’m interested to help on this issue/bug, but currently you may know your code better and therefore could potentially identify the real problem more quickly
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We at adSoul are happy to inform you that everything is working now 🎉
Is ok, take your time 😃