Skip to main content

AFS_AETHER_RECONNECT_MULTIPLIER

Deep-dive reference for:

  • AFS_AETHER_RECONNECT_MULTIPLIER

Status​

  • active

Audience​

  • production/user

Type and Default​

  • Type: floating-point factor (f64).
  • Default: 2.0.
  • Must be greater than 0.

What It Does​

Controls the exponential growth factor for bridge reconnect backoff.

Reconnect delay progression follows the configured backoff policy:

  • start at start_ms
  • multiply by multiplier on each retry
  • apply jitter
  • clamp at max_ms

Higher multipliers back off faster; lower multipliers retry more aggressively.

Where It Applies​

  • Bridge mode reconnect policy used by the changefeed bridge client.
  • Applied together with:
    • AFS_AETHER_RECONNECT_START_MS
    • AFS_AETHER_RECONNECT_MAX_MS
    • AFS_AETHER_RECONNECT_JITTER_PERCENT

Input Surfaces​

  • Env: AFS_AETHER_RECONNECT_MULTIPLIER=<factor>
  • Config file (aether.toml):
    • [bridge.reconnect_backoff]
    • multiplier = <factor>

Resolution and Validation​

Resolution order:

  1. Built-in default (2.0)
  2. aether.toml bridge reconnect block
  3. Env override (AFS_AETHER_RECONNECT_MULTIPLIER)

Validation:

  • Must be numeric and greater than 0.
  • Validated with the rest of the bridge reconnect settings.

Practical Guidance​

  • ~2.0 is a common default and generally reasonable.
  • Use smaller values if you want faster retry cadence under outages.
  • Use larger values to reduce pressure on overloaded servers/network during incidents.

Example​

  • Env:
    • AFS_AETHER_RECONNECT_MULTIPLIER=3.0
  • TOML:
    • [bridge.reconnect_backoff]
    • multiplier = 3.0
  • AFS_AETHER_RECONNECT_START_MS
  • AFS_AETHER_RECONNECT_MAX_MS
  • AFS_AETHER_RECONNECT_JITTER_PERCENT

Primary Implementation Sources​

  • packages/aether/src/config/types/model_defaults.rs
  • packages/aether/src/config/types/config_resolution.rs
  • packages/aether-remote/src/bridge/adapters.rs
  • packages/aether-remote/src/mount/orchestrator.rs