Support question on unlimited timeouts about of-watchdog HOT 9 CLOSED

Hi thanks for raising this issue and for your interest.

IMHO f.ExecTimeout != 0 seems like a bad idea, we should use Golang durations.

I would suggest we add validation in the function that aborts the process if "0s" is set in the code.

Alex

from of-watchdog.

Hi, alexellis. Thank you for your reply.

Why should the function abort if "0s" is set?
README says timeout will be disabled if 0 is set.

Exec timeout for process exec'd for each incoming request (in seconds). Disabled if set to 0.

Is README necessary to be fixed?

from of-watchdog.

The string says 0 not 0s.

Alex

from of-watchdog.

@alexellis i set to 0 but error message given to 0s

functions:
  my-function:
    lang: ruby-http-json
    handler: ./my-function
    image: my-function:latest
    environment:
      exec_timeout: 0

and it's my error;

my-function.1.uy6lq9a36zho@openfaas    | 2020/07/18 19:25:21 Upstream HTTP request error: Post http://127.0.0.1:3000/: context canceled
my-function.1.uy6lq9a36zho@openfaas    | 2020/07/18 19:25:21 Upstream HTTP killed due to exec_timeout: 0s

from of-watchdog.

Why would you set the timeout to 0 seconds, it makes absolutely no sense?

from of-watchdog.

If you're trying to get an unlimited timeout, then you may be barking up the wrong tree, instead, set it as high as you dare - i.e. 10m or 2h

from of-watchdog.

/set title: Support question on unlimited timeouts

from of-watchdog.

/msg: slack

from of-watchdog.

--
Join Slack to connect with the community
https://docs.openfaas.com/community

from of-watchdog.