ECONNRESET when max concurrency is hit
See original GitHub issueWhen more than the max number of concurrent jobs specified in queue.process
are saved, I get the following error:
Error: read ECONNRESET
at errnoException (net.js:904:11)
at TCP.onread (net.js:558:19)
If I up the limit to more than the number of jobs created, there’s no problem. From reading other issues I understand it works as a concurrency control rather than a rate limiter.
How could I make the job wait until the queue can handle it?
Issue Analytics
- State:
- Created 8 years ago
- Comments:11
Top Results From Across the Web
linux - Thousand of concurrent requests - EAI_AGAIN ...
Thousand of concurrent requests - EAI_AGAIN/ECONNRESET error ... I'm running the tests on ubuntu 14.04 & 15.04 and I modified file-max , tcp_fin_timeout ......
Read more >Addressing Networking Errors in a Microservice Based System
While the coreDNS pods were fine, the NodeLocal Cache pods were hitting their max CPU usage and being starved for resources.
Read more >A story of EADDRINUSE and ECONNRESET errors - Gluwer
The ECONNRESET error was silenced before node.js 0.8.20 but not it is not ... but only when there is less than 5 concurrent...
Read more >Request a concurrency limit increase for your Lambda function
The default burst concurrency quota per Region is between 500 and 3,000, which varies per Region. There is no maximum concurrency limit for ......
Read more >Fixing an ECONNRESET error - Postman
The ECONRESET error means that the server unexpectedly closed the connection and the request to the server was not fulfilled. Connection-related ...
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
happy for you, however I can’t see why are you calling
job.failed().error(error)
instead ofdone(err)
. It can be losing your process context in your code, I advise you to passdone
callback in your code contextsFinally figured out why. I was failing jobs with
job.failed(error)
instead ofjob.failed().error(error)
.