Add support for reloading scripts into redis on "NOSCRIPT" errors. #2
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.
This PR deals with functionality to support Redis Sentinel, but the functionality may be useful in certain circumstances even in non-Redis-Sentinel configurations.
We're currently in the process of migrating to Redis Sentinel. We've selected Node Redis Sentinel Client as our sentinel client.
Unfortunately we're experiencing NOSCRIPT errors with Redis Scripto when switching Redis server instances.
This PR modifieds Scripto so to attempt to re-evaluate a script (once) on a NOSCRIPT error. This is useful for sentinel configurations, but also potentially for situations in which a SCRIPT FLUSH has occurred on a single Redis instance (although this is probably a rare situation).