docs(proxy): document --timeout_worker_healthcheck CLI flag - #593
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Adds a CLI reference entry for --timeout_worker_healthcheck, which has been undocumented outside the v1.84.0 release notes since it shipped in BerriAI/litellm#26622
The entry covers what the flag actually controls (the uvicorn multiprocess supervisor's worker health-check window, after which a non-responsive worker is SIGKILLed and replaced), the log lines a kill produces, the uvicorn>=0.37.0 requirement, and the failure mode that motivated this: on older uvicorn the flag is silently ignored apart from a startup warning, and uvicorn's built-in 5 second timeout applies instead. A support case showed an operator running with the flag set to 30 while the effective timeout may well have been 5 seconds, so the entry tells readers to check their startup logs for the warning
Build validated locally with npm run build; the only warnings are pre-existing broken anchors on old release-notes pages untouched by this change