Merged
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates Redis key deletion operations to use batched multi-key deletion, reducing the number of individual Redis commands and mitigating timeouts under heavy load.
- Batch deletes in CompleteAsync by combining multiple key deletion calls into a single call
- Batch deletes in AbandonAsync, DeleteListAsync, and TrimDeadletterItemsAsync to minimize command stacking
ejsmith
approved these changes
Apr 22, 2025
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
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.
Noticed some tests were flakey on the ci. Ran locally using rider until they failed with logging. Noticed the following:
Per https://stackexchange.github.io/StackExchange.Redis/Timeouts#was-there-a-big-request-preceding-several-small-requests-to-the-redis-that-timed-out there is a lot of in work yet to be processed / awaiting response. Also if one of these commands fail while going wide on tasks it will retry them all again.
https://redis.io/docs/latest/commands/unlink/ supports specifying multiple keys at once, thus our payload and commands shouldn't stack up as much in the client.
RemoveAllAsync in the cache client could probably do a much better job at batching these keys as it's not doing that now...