This repository was archived by the owner on Jan 20, 2026. It is now read-only.
Merged
Conversation
philipsu522
approved these changes
Dec 13, 2022
Collaborator
philipsu522
left a comment
There was a problem hiding this comment.
This looks good. I think eviction should be ok, since we will retry anyways. Additionally, this logic seems to be used pretty liberally if at max capacity here https://github.com/sei-protocol/sei-tendermint/blob/main/internal/p2p/router.go#L406
BrandonWeng
added a commit
that referenced
this pull request
Dec 27, 2022
* Error if there's dupe connections * Go Routine * evict * Disconnect and error instead * panic instead * revert panic
Timwood0x10
pushed a commit
to Timwood0x10/sei-tendermint
that referenced
this pull request
Jun 7, 2023
[acl] Add commit access operation to represent end of message
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Describe your changes and provide context
The peers fall into an unrecoverable state if they already have a connection to another peer and they try to connect again.
It seems like Peer A lost its connection to Peer B, but Peer B's mapping was not updated to be aware of this. So when Peer A tries to connect to peer B again, it fails. Therefore if we get a duplicate request where the peer is already connected, we should Error out the existing connection AND return error, this way if it retries it can successfully connect
Testing performed to validate your change
Deployed this in a test cluster and deployed to Peer B, and saw that the Peer A was then able to connect to Peer B again