pub const CONCURRENT_ADDRESS_CHANGE_PERIOD: Duration;
Expand description
The maximum time difference for two address book changes to be considered concurrent.
This prevents simultaneous or nearby important changes or connection progress being overridden by less important changes.
This timeout should be less than:
- the peer reconnection delay, and
- the peer keepalive/heartbeat interval.
But more than:
- the amount of time between connection events and address book updates, even under heavy load (in tests, we have observed delays up to 500ms),
- the delay between an outbound connection failing, and the CandidateSet registering the failure, and
- the delay between the application closing a connection, and any remaining positive changes from the peer.