Replies: 1 comment
-
is the db schema design following a expand and contract pattern? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
So far what I've been doing is to take down the service for 5 mins and apply the schema migration during a litellm version upgrade. Ideally I would want to avoid this downtime if possible, and it became a hassle too since I'm trying to deploy the service as a multi-regional deployment on different clusters.
Does anyone have a recommendation on how to deal with schema migration in production when there's several litellm deployments over different regional k8s clusters?
Beta Was this translation helpful? Give feedback.
All reactions