Number of workers and Error: Redis connection to 127.0.0.1:6379 failed - read ECONNRESET
- Dominant language
- JavaScript
- Stars
- 9.4k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for Kue, it's pretty remarkable.
I'm having a problem with it and I was wondering if Kue has a limit on the number of workers?
In my app I've tried to fork 12 workers using the cluster module. When I run this it very quickly aborts with the error:
`Error: Redis connection to 127.0.0.1:6379 failed - read ECONNRESET`
If I hard-code the number of workers to just 1 it seems to work ok.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names an application using Node.js's cluster module, Kue workers, and Redis at 127.0.0.1:6379, but no repository files or tests. Start by reproducing the failure with 12 workers and compare it with one worker; determine whether Kue imposes a worker limit or why Redis resets the connections. Done means the cause and a verified fix or documented limit are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100