Bugfix - if get_redis_hash finds an invalid key, put it back in the queue. #57
Conversation
This file contains 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.
There should not be any invalid keys, but after calling
LREMon keys that are found to be invalid, several large-scale tests did not complete, leaving keys stranded with statusnew.Putting the keys back has resolved that issue, however, there is a chance that this will cause zip consumers to never scale down as they constantly
RPOPLPUSHinvalid keys, then putting them back.However, despite this risk, I have not seen any large-scale jobs go unfinished with this bugfix.