Enabled the connection to be released.#43
Merged
xin9le merged 9 commits intoxin9le:mainfrom Feb 7, 2025
Merged
Conversation
Merged
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
2 participants
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.
I implemented
IDisposableinRedisConnectionand added aReleaseConnectionmethod so that the internalConnectionMultiplexercould be released.For example, if using Redis on Amazon Elasticache, StackExchange.Redis will not detect that a node has failed over and will not automatically connect to the new node.
Therefore, it is necessary to destroy and recreate the
ConnectionMultiplexerinstance, butRedisConnectiondid not support this functionality.This patch makes it possible.
see: https://tech.guitarrapc.com/entry/2025/01/25/235900
see: StackExchange/StackExchange.Redis#1874