Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't re-establish severed gossip connection until the old connection times out #10

Open
arilotter opened this issue Nov 25, 2024 · 0 comments

Comments

@arilotter
Copy link

I have some program that panics while connected to gossip.
When i restart it, and get it to connect to one of its old peers it used to be connected to, i see
ignoring connection: already accepted peer_id=PublicKey(…) origin=Accept.
Meanwhile, the node attempting to reconnect panics the task with the error: connection closed: connection lost.

This appears to happen because Gossip only wants to maintain one connection per pair, and I'd need to wait for the existing (broken) connection to time out.

It would be great to have an option to forcibly replace any existing connection when sending Command::JoinPeers from a node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant