@kapa.ai: What is the maximum airbyte http read and idle timeout can be set in airbyte 2.0.1 helm chart?

Airbyte has several different timeout settings depending on the context: Sync Job Timeout The maximum duration for a sync job is controlled by the

SYNC_JOB_MAX_TIMEOUT_DAYS

environment variable, which defaults to 3 days. The minimum configurable value is 1 day. You can increase this value in your

.env

file if needed (a restart of the worker and scheduler is required after changing it). [Sync hangs until I cancel] Source Heartbeat Timeout The maximum time allowed between messages from the source is configured via

heartbeat-max-seconds-between-messages

in

flags.yaml

. The default is 3 hours. If no message is received within this window, the sync is failed with the message "The source is unresponsive." [Heartbeats] Destination Timeout The destination timeout is configured via

destination-timeout-max-seconds

in

flags.yaml

. The default is 24 hours. If a call to the destination exceeds this duration, the sync is failed with "The destination is unresponsive." [Heartbeats] Schema Discovery Timeout For schema discovery (the

discover

mechanism), the timeout can be configured in

values.yaml

for Kubernetes deployments. For example: [Scaling Airbyte]

server:
  httpIdleTimeout: 20m
  extraEnv:
    - name: READ_TIMEOUT
      value: 30m

Airflow Operator Timeout When using the Airflow Airbyte operator, the

AirbyteTriggerSyncOperator

has a

timeout

parameter (maximum seconds to wait for the job to complete) that defaults to 3600 seconds (1 hour). [Airflow Airbyte Provider] In summary, the overall maximum sync job timeout is 3 days by default (

SYNC_JOB_MAX_TIMEOUT_DAYS=3

), which is the broadest timeout governing how long a sync can run end-to-end. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.