ETIMEDOUT errors after app has been running couple of hours

[hannta]

Im running node app which connects to external api using got. After the app has been running few hours with decent traffic, it starts to time out when connecting to external api. If the app is restarted, connection issues are resolved.

Sounds like something is leaking something?

System:
Nodejs 16.19.0
Debian 11

Got setup:

got.extend({
  prefixUrl: apiUrl,
  method: 'POST',
  http2: true,
  retry: { limit: 1 },
  timeout: { request: 5000 },
  headers: {
    'content-type': 'application/graphql',
    'user-agent': serverUserAgent,
    ...requestHeaders,
  },
});

"RequestError: Timeout awaiting 'request' for 5000ms\n
    at ClientRequest.<anonymous> (/var/www/my-api-app/source/node_modules/got-cjs/dist/source/core/index.js:802:68)\n
    at Object.onceWrapper (node:events:628:26)\n
    at ClientRequest.emit (node:events:525:35)\n
    at ClientRequest.origin.emit (/var/www/my-api-app/source/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)\n
    at emitErrorNT (node:internal/streams/destroy:157:8)\n
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n
    at processTicksAndRejections (node:internal/process/task_queues:83:21)\n
    at Timeout.timeoutHandler [as _onTimeout] (/var/www/my-api-app/source/node_modules/got-cjs/dist/source/core/timed-out.js:49:25)\n
    at listOnTimeout (node:internal/timers:561:11)\n
    at processTimers	

timings:
{
   "start": 1674680587120,
   "socket": 1674680587120,
   "error": 1674680592121,
   "phases": {
   	"wait": 0,
   	"total": 5001
   }
}

[sindresorhus]

There's not enough important here for us to help. But I would try with http2 set to false and see if that helps. HTTP2 support has be notoriously buggy in Node.js. Trying out Node.js 18 may also be a good idea.

[hannta]

I upgraded to Node 18.13.0, so far it looks good, but I know more next week when the app gets more load.

This has been tricky to debug, Im not able to reproduce connection issues locally. In prod if app has good amount of load, it is matter of few hours when the connection issues start. With smaller load it might work ok for entire day.

[hannta]

• After upgrading Node.js to 18.13.0 the connection issue is still there. I do not have exact metrics but, the issue occurs much more rarely now after Node.js upgrade.
• When switching http2 to false, the issue is not occurring any more.