CLO-171: balancerd: retry DNS resolution at startup with backoff - #37992
Open
jubrad wants to merge 1 commit into
Open
CLO-171: balancerd: retry DNS resolution at startup with backoff#37992jubrad wants to merge 1 commit into
jubrad wants to merge 1 commit into
Conversation
During upgrades, balancerd may start before the target environmentd service's DNS name is resolvable. Previously this caused an immediate panic. Now balancerd retries DNS resolution with exponential backoff (starting at 250ms, clamped to 2s) until the configurable timeout is reached (default 30s). A new `--static-resolver-addr-timeout` CLI flag (or `STATIC_RESOLVER_ADDR_TIMEOUT` env var) controls how long to wait. Fixes CLO-171. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
jubrad
marked this pull request as ready for review
July 31, 2026 19:07
jubrad
enabled auto-merge (squash)
July 31, 2026 19:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
During upgrades, balancerd may start before the target environmentd service's DNS name is resolvable. Previously this caused an immediate panic:
This PR adds retry logic with exponential backoff to handle transient DNS resolution failures at startup.
--static-resolver-addr-timeoutorSTATIC_RESOLVER_ADDR_TIMEOUTenv var)Test plan
cargo test -p mz-balancerd)cargo check -p mz-balancerdpassesFixes https://linear.app/materializeinc/issue/CLO-171/balancerd-panic-due-to-dns-resolution-failure
🤖 Generated with Claude Code