docs(proxy): document rate limiter opt-out env vars - #334
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 reference entries for two environment variables introduced in BerriAI/litellm#30211 to the environment variables reference table in docs/proxy/config_settings.md.
LITELLM_TPM_TOKEN_RESERVATION_ENABLED controls whether the v3 rate limiter reserves TPM tokens upfront; when false it skips the reservation and enforces TPM post-call from actual usage. REDIS_CIRCUIT_BREAKER_ENABLED lets operators turn the Redis circuit breaker off entirely so it never opens. Both default to true.
This pairs with BerriAI/litellm#30211, which is blocked on these variables being documented here; the litellm CI check tests/documentation_tests/test_env_keys.py fails until every env var read from the code appears in this table. I verified locally by pointing the test at the edited file and it now exits 0.