Question: how to deal with connection timeouts?

node.js version: v11.0.0 npm/yarn version: 6.4.1 faktory-server version: 0.9.1

facktory-worker package version:

Code sample:

Error: read ETIMEDOUT
  at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'read'
Unhandled Rejection at: Promise Promise {
  <rejected> Error: Connection closed
      at Client.onClose (/app/node_modules/faktory-worker/lib/client.js:327:26)
      at Socket.emit (events.js:182:13)
      at Socket.EventEmitter.emit (domain.js:442:20)
      at TCP._handle.close (net.js:606:12)

This means I should check for errors? If this error happens there is no reconnection to faktory (never starts processing jobs)

[jbielick]

I consider the second part of this issue—not reconnecting and ceasing job processing—to be an outstanding issue and I’ll start working on that as well.

This should be resolved in v3.0.0

[jbielick]

@aledbf

Thanks for the info.

I overlooked setting keepalive on the TCP socket for this library. It’s been enabled and a new version published @ v.2.2.2 on npm. I suspect kube-proxy (?) or the faktory server itself was disconnecting due to inactivity.

I consider the second part of this issue—not reconnecting and ceasing job processing—to be an outstanding issue and I’ll start working on that as well.