Open yogiben opened 7 years ago
Socket timeouts not being caught
I found if there are too many async requests, then ESOCKETTIMEDOUT exception happens in linux. The workaround I've found is doing this:
setting this options to request():
agent: false, pool: {maxSockets: 100}
Notice that after that, the timeout can be lying so you might need to increase it. Also I think this could be solved by increasing ulimits number of file opened maximum in linux.
@cancerberoSgx if the ulimits were the problem, then the error would be EMFILE
I found if there are too many async requests, then ESOCKETTIMEDOUT exception happens in linux. The workaround I've found is doing this:
setting this options to request():
agent: false, pool: {maxSockets: 100}
Notice that after that, the timeout can be lying so you might need to increase it. Also I think this could be solved by increasing ulimits number of file opened maximum in linux.
but It doesn't work
This still happens to me, nothing seems to work. Too many parallels requests cause this.
We're getting the following uncaught error originating from request.js
We're using
try
catch
and promises wherever possible.