Cowboy idle_timeout of 60s breaks long-running model API invocations

[VolkerStolz]

The current runtime uses Cowboy's default timeout of 60s. If a method call through the model API takes longer, Cowboy will drop the connection, which leads on the caller side e.g. to an curl: (52) Empty reply from server, and somehow leaves the affected object unusable.

Completely disabling idle_timeout might be infinity.

We could raise the default and/or make it configurable. Additionally, we might want to investigate what happens to the state of objects that get hit by that.

• https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_http/

[rudi]

I’d be ok with turning off timeouts until someone finds problems with that - we’re not going for the long-running, high-availability server market here :)

…

Sent from my iPhone

On 7 Jun 2021, at 18:02, Volker Stolz ***@***.***> wrote:  The current runtime uses Cowboy's default timeout of 60s. If a method call through the model API takes longer, Cowboy will drop the connection, which leads on the caller side e.g. to an curl: (52) Empty reply from server, and somehow leaves the affected object unusable. Completely disabling idle_timeout might be infinity. We could raise the default and/or make it configurable. Additionally, we might want to investigate what happens to the state of objects that get hit by that. https://ninenines.eu/docs/en/cowboy/2.7/manual/cowboy_http/ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.