Timeouts

[SEAPUNK]

Runners' transports have timeouts, but not the runners themselves.

In the case of the HTTP transport:

• timeout (Number): Sets the timeout.check and timeout.update values.

...

• timeout.check = 120000: How long to wait before timing out request to server checking for jobs to process
• timeout.update = 120000: How long to wait before timing out request to server updating job run status

---

Jobs have three timeouts:

• timeout (Number): Sets the timeout.total value.

...

• timeout.total = 120000: The "total" timeout, how long a job can be in the server before giving up. This is idle time + run time. This timeout is used if defined along with timeout.idle and timeout.run.

OR

• timeout.idle = 120000: How long a job can be in queue before giving up.
• timeout.run = 120000: How long a job can be running before giving up.

---

Server (and server transports) have one timeout:

• timeout (Number): Sets the timeout.client value.

...

• timeout.client = 120000: How long a client (runner or subscriber) be unresponsive before cleaning up resources related to the client(s).

---

Timeouts of 0 = no timeout.

[SEAPUNK]

• [ ] Can we do timeout = -1 instead? The algorithm I wrote for determining job timeouts is stupid long.