-
Notifications
You must be signed in to change notification settings - Fork 801
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
Make concurrent dialing more aggressive #3656
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,7 +22,7 @@ use either::Either; | |
use libp2p::{ | ||
core::{ | ||
muxing::StreamMuxerBox, | ||
transport::{Boxed, OptionalTransport}, | ||
transport::{timeout::TransportTimeout, Boxed, OptionalTransport}, | ||
upgrade, | ||
}, | ||
dns, identity, noise, tcp, websocket, PeerId, Transport, TransportExt, | ||
|
@@ -31,6 +31,9 @@ use std::{sync::Arc, time::Duration}; | |
|
||
pub use libp2p::bandwidth::BandwidthSinks; | ||
|
||
/// Timeout after which a TCP connection attempt is considered failed. | ||
const TCP_DIAL_TIMEOUT: Duration = Duration::from_secs(20); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. dq: The default timeout is in the order of minutes? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. On my linux box it's 2 min 10 secs. |
||
|
||
/// Builds the transport that serves as a common ground for all connections. | ||
/// | ||
/// If `memory_only` is true, then only communication within the same process are allowed. Only | ||
|
@@ -56,7 +59,8 @@ pub fn build_transport( | |
let transport = if !memory_only { | ||
// Main transport: DNS(TCP) | ||
let tcp_config = tcp::Config::new().nodelay(true); | ||
let tcp_trans = tcp::tokio::Transport::new(tcp_config.clone()); | ||
let tcp_trans = | ||
TransportTimeout::new(tcp::tokio::Transport::new(tcp_config.clone()), TCP_DIAL_TIMEOUT); | ||
let dns_init = dns::TokioDnsConfig::system(tcp_trans); | ||
|
||
Either::Left(if let Ok(dns) = dns_init { | ||
|
@@ -65,15 +69,20 @@ pub fn build_transport( | |
// Main transport can't be used for `/wss` addresses because WSS transport needs | ||
// unresolved addresses (BUT WSS transport itself needs an instance of DNS transport to | ||
// resolve and dial addresses). | ||
let tcp_trans = tcp::tokio::Transport::new(tcp_config); | ||
let tcp_trans = | ||
TransportTimeout::new(tcp::tokio::Transport::new(tcp_config), TCP_DIAL_TIMEOUT); | ||
let dns_for_wss = dns::TokioDnsConfig::system(tcp_trans) | ||
.expect("same system_conf & resolver to work"); | ||
Either::Left(websocket::WsConfig::new(dns_for_wss).or_transport(dns)) | ||
} else { | ||
// In case DNS can't be constructed, fallback to TCP + WS (WSS won't work) | ||
let tcp_trans = tcp::tokio::Transport::new(tcp_config.clone()); | ||
let desktop_trans = websocket::WsConfig::new(tcp_trans) | ||
.or_transport(tcp::tokio::Transport::new(tcp_config)); | ||
let tcp_trans = TransportTimeout::new( | ||
tcp::tokio::Transport::new(tcp_config.clone()), | ||
TCP_DIAL_TIMEOUT, | ||
); | ||
let tcp_trans_for_ws = | ||
TransportTimeout::new(tcp::tokio::Transport::new(tcp_config), TCP_DIAL_TIMEOUT); | ||
let desktop_trans = websocket::WsConfig::new(tcp_trans_for_ws).or_transport(tcp_trans); | ||
Either::Right(desktop_trans) | ||
}) | ||
} else { | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dq: I think this is fine, but do you think there is a chance we might run into issues with the total number of file descriptors opened for the concurrent requests? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is theoretically possible, especially for nodes with high out peer count. All my systems show
ulimit -n
as 1024. So, it means maximum 125 simultaneous connections to peers with bloated DHT records before the change, and 60 connections after the change.Don't think the practical probability of hitting that many peers at once with bloated DHT records is high, but at least something to keep in mind.