fix: prevent shard skip in ListActors when SCAN returns oversized batch#328
Open
Mesut Oezdil (mesutoezdil) wants to merge 1 commit into
Open
Conversation
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.
Redis SCAN COUNT is a hint and not a cap.
When SCAN returns more keys than remaining and cursor reaches 0 in the same call, the outer loop advances to the next shard where remaining<=0 triggers immediately.
The next-token then points to the shard after that, permanently skipping one shard's actors from all subsequent pages.
Fix: set stop=true when cursor==0 and result is already at or over pageSize.