Skip to content

Trafficserver has additional timeout not tied to configuration #441

@science695

Description

@science695

I have been trying to get an api long-running process (more than 15 minutes) to run through umbrella.

I have set all 3 nginx timeouts to 3600 seconds, but it keeps getting a gateway timeout at 900 (15minutes).

I found a setting in trafficserver/records.config:

CONFIG proxy.config.http.transaction_active_timeout_in INT 900

It seems like this setting shold also be tied to proxy_read_timeout like

config["trafficserver"]["_transaction_no_activity_timeout_out"] = config["nginx"]["proxy_read_timeout"]

Is there any danger of setting this in the api-umbrella.yml config file:

trafficserver:
  embedded_server_config:
    records:
      - "CONFIG proxy.config.http.transaction_active_timeout_in INT 3600"
      - "CONFIG proxy.config.http.connect_attempts_timeout INT 3600"
      - "CONFIG proxy.config.http.post_connect_attempts_timeout INT 3600"

or setting it to 0 so it doesn't introduce another timeout to the process?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions