Handle correctly servers not initiating close#6
Open
adrianlzt wants to merge 1 commit intojamescun:masterfrom
Open
Handle correctly servers not initiating close#6adrianlzt wants to merge 1 commit intojamescun:masterfrom
adrianlzt wants to merge 1 commit intojamescun:masterfrom
Conversation
If we use the default handler to a Redis server, Switcher will keep the connection open forever, because Redis server is not going to initiate the close of the connection. With this new scheme, as soon as one channel has finished sending data, the two connections are closed and Shovel could finish. This follows the pattern seen in https://github.com/google/tcpproxy/blob/master/tcpproxy.go#L386
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.
If we use the default handler to a Redis server, Switcher will keep the
connection open forever, because Redis server is not going to initiate
the close of the connection.
With this new scheme, as soon as one channel has finished sending data,
the two connections are closed and Shovel could finish.
This follows the pattern seen in https://github.com/google/tcpproxy/blob/master/tcpproxy.go#L386