eclipse-ditto / ditto

Eclipse Ditto™: Digital Twin framework of Eclipse IoT - main repository

Home Page:https://eclipse.dev/ditto/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

nginx timeout is not configurable in helm chart

dimabarbul opened this issue · comments

Our use case is that we want to extend timeout for live messages to about 2 minutes. We configured all required timeouts for gateway service to be 115 seconds (slightly lower than 2 minutes due to limitation discussed at How to increase message timeout to 5 minutes?).

We install Ditto using helm chart and it looks like maximum timeout that nginx provides in hardcoded to 70 seconds:

      # timeouts are configured slightly higher than ditto-eclipse-ditto-gateway read-timeout of 60 seconds
      proxy_connect_timeout 70; # seconds, default: 60
      proxy_send_timeout 70; # seconds, default: 60
      proxy_read_timeout 70; # seconds, default: 60
      # will try another upstream if an error or timeout occurred during the connection
      # or if the upstream returns 502 response
      proxy_next_upstream error timeout http_502;
      # will retry up to 3 times to find another upstream to connect to
      proxy_next_upstream_tries 3;
      # will try for max. 20s to find another upstream to connect to
      proxy_next_upstream_timeout 20;

      send_timeout 70; # seconds, default: 60

It would be great if it was configurable.