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

Don't hammer disconnecting peers #299

Closed
wants to merge 1 commit into from

Conversation

buck54321
Copy link
Contributor

A peer disconnect can trigger immediate reconnects to the same peer regardless of the nature of the disconnect.

Starting at (*Peer).Disconnect, closing the quit channel causes WaitForDisconnect to return in peerDoneHandler, which sends a message to handleDonePeerMsg. For non-persistent peers, this can cause two simultanous calls to GetNewAddress. Once more directly via NewConnReq, and once via (*ConnManager).Remove sending a handleDisconnected to the (*ConnManager).connHandler and (*ConnManager).handleFailedConn, which calls NewConnReq again. So a disconnecting peer can trigger two new connection requests immediately, and there's nothing preventing the same address from being used.

The newAddressFunc used by *server in btcd may also benefit from this change. I think it might be the reason for the // TODO: duplicate oneshots? comment.

@Chinwendu20
Copy link
Contributor

If I understand correctly, you are saying that disconnecting a peer can lead to immediate reconnection.
You went further to state that this connection request happens twice for non persistent peers as disconnecting them would lead to a call to GetNewAddressFunc twice?

  1. As a result of the call to the Remove method of the connmanager
  2. Then here as well when a NewConnReq method is called directly

Right?
For the first case, this specifically occurs during a call to the handleFailedConn here

Are my following correctly?

@buck54321
Copy link
Contributor Author

Yes. That's correct.

@Chinwendu20
Copy link
Contributor

@buck54321
Copy link
Contributor Author

Oooh. OK. Hmm. I'm seeing little clusters of calls to the same address. Up to 5 at a time unmetered on a loosely connected testnet. I've traced the clusters to mostly handleFailedConn and handleDonePeerMsg buy maybe I'm misunderstanding the nature. Lemme look a little closer.

@buck54321
Copy link
Contributor Author

I can't reliably reproduce. Will reopen if I figure something out.

@buck54321 buck54321 closed this May 10, 2024
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

Successfully merging this pull request may close these issues.

2 participants