Repository navigation
Fix client 502/503 on deploy: start_period 60s + lb retries - #111
Merged
Merged
Conversation
Same fix as dnd-management-nra#65/#66: - client's healthcheck start_period bumped from 30s to 60s to match server, giving Caddy's independent active health check enough time to confirm the new container before Swarm's start-first update retires the old one. - caddy.reverse_proxy.lb_try_duration/lb_retries added so a request landing on the old container while it drains after SIGQUIT (still "running" in Docker's eyes, but refusing new connections) transparently retries against the healthy upstream instead of surfacing 502/503. Co-Authored-By: Claude Sonnet 5 <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
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
Same fix verified working on
dnd-management-nra(#65, #66), applied here:client's healthcheckstart_periodbumped from 30s to 60s to matchserver— gives Caddy's independent active health check enough time to confirm the new container healthy before Swarm'sstart-firstrolling update retires the old one.caddy.reverse_proxy.lb_try_duration: 5s/lb_retries: 3added toclient's labels — a request landing on the old container while it drains afterSIGQUIT(still "running" per Docker, but refusing new connections) now transparently retries against the healthy upstream instead of surfacing 502/503 to the browser.Test plan
client.Generated by Claude Code