-
-
Notifications
You must be signed in to change notification settings - Fork 11.6k
fix(proxy): make spend counter reseed idempotent across pods via SET NX #28590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
silencedoctor
wants to merge
1
commit into
BerriAI:litellm_internal_staging
from
silencedoctor:fix/spend-counter-reseed-idempotent
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When N pods all lose the
SET NXrace (key was set by another pod) and then the winner's key expires before each loser'sGETreturns, all N losers fall into theasync_increment(db_spend)branch. SinceINCRBYFLOATon a non-existent key starts from 0, the final counter ends up at(N-1) * db_spend. This is identical to the race the fix is designed to prevent, just in a much narrower window — the key must expire within the round-trip of a single Redis call. The PR description acknowledges this, and the existingcoalesced_window()already uses the same pattern, so this is a deliberate trade-off rather than a new regression.