DF_HTTP_TIMEOUT_SECS

HTTP client timeout in seconds for all control-plane and compute-engine requests. Set to 0 or `none` to disable the timeout entirely. Default: 1800 (30 minutes).

Syntax

DF_HTTP_TIMEOUT_SECS=<SECONDS>|0|none

Description

## Overview `DF_HTTP_TIMEOUT_SECS` controls the per-request timeout of the reqwest HTTP client used for every call the CLI makes, to both the control plane and to compute engines. It bounds how long the CLI will wait for a single response before returning a timeout error. The default of 30 minutes is generous enough for most interactive workloads but too short for large OPTIMIZE, VACUUM, or multi-hour ETL runs. ## Behavior - Read at CLI startup; the parsed value is baked into the HTTP client at construction time. - Default when unset: `1800` seconds (30 minutes). - Accepts a positive integer count of seconds. - Accepts the sentinel `0` or the literal string `none` to build the HTTP client with no timeout at all. - Applies uniformly to every HTTP call in the process: auth, compute-node discovery, statement execution, SSE initialisation. - This setting does not cancel server-side work. It controls only how long the client waits for bytes; if it expires the client aborts the request but the engine may keep running the statement. ## Resolution - `DF_HTTP_TIMEOUT_SECS` env var - Built-in default `1800`

Examples

# Two-hour timeout for a long ETL
DF_HTTP_TIMEOUT_SECS=7200 delta-forge-cli run long-etl.sql

# Disable the timeout entirely for a full-table OPTIMIZE
DF_HTTP_TIMEOUT_SECS=none delta-forge-cli query OPTIMIZE sales.orders

# `0` is an alias for `none`
DF_HTTP_TIMEOUT_SECS=0 delta-forge-cli

# Shorten the timeout for an interactive session against a flaky network
export DF_HTTP_TIMEOUT_SECS=60
delta-forge-cli

# CI step with explicit long timeout
- name: Run nightly compaction
  env:
    DF_HTTP_TIMEOUT_SECS: '10800'
  run: delta-forge-cli run maintenance/compact.sql

Pitfalls

• `DF_HTTP_TIMEOUT_SECS=0` and `=none` both disable the timeout entirely. If the compute node hangs, the CLI will wait forever with no client-side escape; kill the process manually.
• The timeout is applied to every request, not just the statement execution. Very small values (for example `5`) can cause auth and catalog lookups against a remote control plane to fail before they complete.
• Raising the timeout on the CLI does not change any timeout on a reverse proxy or load balancer sitting in front of the control plane. A 504 from an intermediary will still terminate the request even with `DF_HTTP_TIMEOUT_SECS=none`.

See Also

• CLI_RUN