fix: one peer occupy multiple tcp connections#2262
Merged
garyyu merged 5 commits intomimblewimble:masterfrom Dec 31, 2018
garyyu:2258
Merged
fix: one peer occupy multiple tcp connections#2262garyyu merged 5 commits intomimblewimble:masterfrom garyyu:2258
garyyu merged 5 commits intomimblewimble:masterfrom
garyyu:2258
Conversation
Contributor
Author
|
Tested in 3 servers for 8 hours, the effect is quite good, no more hundreds of connections. But for 100% avoid multiple tcp connections on one peer, we need more actions: |
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
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.
To close #2258
And it doesn't make sense to retry in 1 second on any error, and we already have a resurrection mechanism for those
p2p::State::Defunctpeers.