You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In LiteLLM v1.61.20-stable, when deploying multiple instances, modifying the TPM (transactions per minute) and RPM (requests per minute) of a virtual key on instance A does not reflect the changes on instance B, which still retrieves the original TPM and RPM values.
first:instance A and instance B virtual key tpm 70
second:change instance B virtual key tpm 80
all instance virtual key settings ui can see virtual key tpm 80,but instance A api return tpm 70
Relevant log output
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.61.20-stable
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered:
What happened?
In LiteLLM v1.61.20-stable, when deploying multiple instances, modifying the TPM (transactions per minute) and RPM (requests per minute) of a virtual key on instance A does not reflect the changes on instance B, which still retrieves the original TPM and RPM values.
first:instance A and instance B virtual key tpm 70
second:change instance B virtual key tpm 80
all instance virtual key settings ui can see virtual key tpm 80,but instance A api return tpm 70
Relevant log output
Are you a ML Ops Team?
No
What LiteLLM version are you on ?
v1.61.20-stable
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: