feat(worker): use lightweight liveness & add Celery readiness probe #1923
+31
−3
Conversation
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.
This update prevents worker pods from restart loops caused by Celery ping timeouts.
Liveness probe: replaced the Celery ping with a lightweight command (
rm -f /tmp/health.txt) to only check container health.Readiness probe: added an optional Celery app.control.ping() check with configurable timeout (
celeryTimeoutSeconds).The liveness probe now ensures the container is alive, while readiness reflects broker connectivity - avoiding restarts when Celery or the broker is slow (increase
celeryTimeoutSecondsto allow the process to complete)