docs(proxy): document LITELLM_SKIP_INDEX_MIGRATIONS - #1178
Open
yuneng-berri wants to merge 3 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
6 tasks
…INDEX_MIGRATIONS too
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.
Documents the new
LITELLM_SKIP_INDEX_MIGRATIONSenv var from BerriAI/litellm#39666: a "Skip index builds on a large database" section in the production guide, and a row in the config settings referenceWith the variable set to
true, the proxy records index-only migrations as applied at boot without running them, so an operator with a very largeLiteLLM_SpendLogstable can take a release like BerriAI/litellm#37983 and build the index themselves withCREATE INDEX CONCURRENTLYinstead of holding a table lock during boot. The new section shows the exact statement to run afterwards and notes that--use_prisma_db_pushignores the flag