Increase Caddy retry window to reduce deploy 502s#67
Open
Conversation
The 5s/250ms retry settings weren't always enough to cover the litestream + Go startup during deploys, causing brief 502s. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
lb_try_durationfrom 5s → 10s andlb_try_intervalfrom 250ms → 100msTest plan
Further improvements if 502s persist
Socket activation (zero-downtime)
Add a
wppackages.socketunit so the kernel holds the listening socket open across restarts. Requires a Go code change to accept the fd viaSD_LISTEN_FDS(e.g.go-systemd). This is the most robust option — no requests are dropped because the listen backlog buffers them while the new process starts.Health-checked restart
Replace the
systemctl restartin the deploy playbook with a start + health poll loop, so Ansible doesn't return until the new process is confirmed ready. Catches startup failures earlier but doesn't fully eliminate the gap on its own.🤖 Generated with Claude Code