AFS_AETHER_RECONNECT_MAX_MS
Deep-dive reference for:
AFS_AETHER_RECONNECT_MAX_MS
Status
active
Audience
production/user
Type and Default
- Type: unsigned integer milliseconds (
u64). - Default:
60000ms (60s). - Must be greater than
0. - Must be greater than or equal to
AFS_AETHER_RECONNECT_START_MS.
What It Does
Sets the maximum delay cap for bridge reconnect exponential backoff.
Reconnect delay grows from start_ms by multiplier, with jitter applied, but never exceeds max_ms.
This prevents reconnect delays from growing unbounded during prolonged outages.
Where It Applies
- Bridge mode reconnect policy used by the changefeed bridge client.
- Applied together with:
AFS_AETHER_RECONNECT_START_MSAFS_AETHER_RECONNECT_MULTIPLIERAFS_AETHER_RECONNECT_JITTER_PERCENT
Input Surfaces
- Env:
AFS_AETHER_RECONNECT_MAX_MS=<ms> - Config file (
aether.toml):[bridge.reconnect_backoff]max_ms = <ms>
Resolution and Validation
Resolution order:
- Built-in default (
60000) aether.tomlbridge reconnect block- Env override (
AFS_AETHER_RECONNECT_MAX_MS)
Validation:
- Must be >
0. - Backoff validation enforces
max_ms >= start_ms. - Other backoff parameters are validated together in the same bridge backoff block.
Practical Guidance
- Use lower values when you want faster retry pressure and shorter worst-case reconnect pauses.
- Use higher values to reduce load during long outages.
- Keep
max_msandstart_msconsistent; avoid tinymax_mswith aggressive multiplier if you want smoother spread.
Example
- Env:
AFS_AETHER_RECONNECT_MAX_MS=90000
- TOML:
[bridge.reconnect_backoff]max_ms = 90000
Related Variables
AFS_AETHER_RECONNECT_START_MSAFS_AETHER_RECONNECT_MULTIPLIERAFS_AETHER_RECONNECT_JITTER_PERCENT
Primary Implementation Sources
packages/aether/src/config/types/model_defaults.rspackages/aether/src/config/types/config_resolution.rspackages/aether-remote/src/bridge/adapters.rspackages/aether-remote/src/mount/orchestrator.rs