AFS_AETHER_RECONNECT_START_MS
Deep-dive reference for:
AFS_AETHER_RECONNECT_START_MS
Status
active
Audience
production/user
Type and Default
- Type: unsigned integer milliseconds (
u64). - Default:
1000ms (1s). - Must be greater than
0. - Must be less than or equal to
AFS_AETHER_RECONNECT_MAX_MS.
What It Does
Sets the initial delay for bridge reconnect exponential backoff.
On reconnect attempts, the delay starts at start_ms, then grows by multiplier,
with jitter applied, and is capped by max_ms.
This value controls how quickly the first retry happens after a disconnect/error.
Where It Applies
- Bridge mode reconnect policy used by the changefeed bridge client.
- Applied together with:
AFS_AETHER_RECONNECT_MAX_MSAFS_AETHER_RECONNECT_MULTIPLIERAFS_AETHER_RECONNECT_JITTER_PERCENT
Input Surfaces
- Env:
AFS_AETHER_RECONNECT_START_MS=<ms> - Config file (
aether.toml):[bridge.reconnect_backoff]start_ms = <ms>
Resolution and Validation
Resolution order:
- Built-in default (
1000) aether.tomlbridge reconnect block- Env override (
AFS_AETHER_RECONNECT_START_MS)
Validation:
- Must be >
0. - Backoff validation enforces
max_ms >= start_ms. - Other reconnect parameters are validated together in the same block.
Practical Guidance
- Lower values retry sooner after failures but can increase reconnect pressure.
- Higher values reduce immediate retry pressure but slow recovery.
- Keep this aligned with your
max_msandmultipliergoals.
Example
- Env:
AFS_AETHER_RECONNECT_START_MS=1500
- TOML:
[bridge.reconnect_backoff]start_ms = 1500
Related Variables
AFS_AETHER_RECONNECT_MAX_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