fix(deploy): raise app healthcheck start_period to 120s - #401
Open
keysersoft wants to merge 1 commit into
Open
Conversation
First boot takes ~100s (migrations + Next.js warmup); the 30s start_period marked the v0.3.3 deploy unhealthy moments before the app came up, failing the pipeline even though the rollout succeeded.
|
This PR has been quiet for 30 days. If you're still working on it, leave a comment so we don't auto-close it in 14 days. |
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.
The v0.3.3 deploy was marked failed by the
--waithealth gate even though the rollout succeeded: the app needs ~100s on first boot (migrations + Next.js warmup) and the healthcheck only allowed ~80s (30s start_period + 5×10s retries). 120s gives it room without weakening the gate.