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.
Worker did not remove the event listener when it ended.
See original GitHub issueHi, I’ve found the following warning message.
(node:80974) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 21 end listeners added to [Redis].
Use emitter.setMaxListeners() to increase limit
And then investigated it. As a result, First, the multi-worker had been running one or two if the queue is empty. Second, Each worker added the event listener into the Redis when the worker started. Finally, any worker did not remove the event listener when it ended.
As the time goes the event listener adds infinitely.
I think when the worker ends - in the end method of the worker, it should remove the event listener in the Redis.
Please let me know your opinion. Thanks.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (3 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
Amazing - please submit a PR with the fix, and I’ll get a release out quickly!
I’m not sure I have enough familiarity w/ the codebase to contribute atm 😦