fix: start probe server before dependency init to prevent startup probe failures#296
Merged
Merged
Conversation
luis5tb
force-pushed
the
worktree-agent-health
branch
from
ea9af1b to
f141e34
Compare
luis5tb
force-pushed
the
worktree-agent-health
branch
from
f141e34 to
eaec211
Compare
…be failures The probe server on port 8002 was starting after Redis, database, and service control initialization, so the Cloud Run startup probe had no endpoint to reach during that window. With only 35s allowed (3 failures × 10s + 5s delay), slow dependency connections caused the probe to fail and the deployment to abort. Move probe server startup to the top of the lifespan so /health responds immediately, and increase failureThreshold from 3 to 18 (~185s window). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
luis5tb
force-pushed
the
worktree-agent-health
branch
from
eaec211 to
8347889
Compare
IlonaShishov
added a commit
to IlonaShishov/google-lightspeed-agent
that referenced
this pull request
Jun 24, 2026
The probe server was moved to the top of lifespan in PR RHEcosystemAppEng#296. The rebase left a stale copy at the old location — remove it. 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
2 participants
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 probe server on port 8002 was starting after Redis, database, and service control initialization, so the Cloud Run startup probe had no endpoint to reach during that window. With only 35s allowed (3 failures × 10s + 5s delay), slow dependency connections caused the probe to fail and the deployment to abort.
Move probe server startup to the top of the lifespan so /health responds immediately, and increase failureThreshold from 3 to 18 (~185s window).