-
Notifications
You must be signed in to change notification settings - Fork 446
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor!: remove per-peer parallel dialling (#2090)
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across a single peers' multiaddrs. Closes #2090
- Loading branch information
1 parent
d8f5bc2
commit bf9f303
Showing
7 changed files
with
51 additions
and
224 deletions.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
<!--Specify versions for migration below--> | ||
# Migrating to [email protected].0 <!-- omit in toc --> | ||
# Migrating to [email protected] <!-- omit in toc --> | ||
|
||
A migration guide for refactoring your application code from libp2p `v0.46` to `v1.0.0`. | ||
|
||
|
@@ -16,6 +16,7 @@ A migration guide for refactoring your application code from libp2p `v0.46` to ` | |
- [Plaintext](#plaintext) | ||
- [Pnet](#pnet) | ||
- [Metrics](#metrics) | ||
- [Connection Manager](#connection-manager) | ||
|
||
## AutoNAT | ||
|
||
|
@@ -311,3 +312,11 @@ The following metrics were renamed: | |
|
||
`libp2p_dialler_pending_dials` => `libp2p_dial_queue_pending_dials` | ||
`libp2p_dialler_in_progress_dials` => `libp2p_dial_queue_in_progress_dials` | ||
|
||
## Connection Manager | ||
|
||
The observed behavior of dialing peers has been that given a list of supported addresses, if any one routable address would succeed then all would succeed and that if any routable address would fail then all would fail. | ||
|
||
Consequently the previous dial behaviour of dialing all available addresses (up to a concurrency limit) and cancelling any in-flight dials when the first succeeds was a very inefficient use of resources. | ||
|
||
Since `[email protected]` we have only dialed one address at a time for each peer by setting the default value of the `ConnectionManager`'s `maxParallelDialsPerPeer` option to `1`. As of `[email protected]` this option has been removed. |
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
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
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
Oops, something went wrong.