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

v1.17: separates out routing shreds from establishing connections (backport of #33599) #33772

Merged
merged 1 commit into from
Oct 20, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 19, 2023

This is an automatic backport of pull request #33599 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

Currently each outgoing shred will attempt to establish a connection if
one does not already exist. This is very wasteful and consumes many
tokio tasks if the remote node is down or unresponsive.

The commit decouples routing packets from establishing connections by
adding a buffering channel for each remote address. Outgoing packets are
always sent down this channel to be processed once the connection is
established. If connecting attempt fails, all packets already pushed to
the channel are dropped at once, reducing the number of attempts to make
a connection if the remote node is down or unresponsive.

(cherry picked from commit 8becb72)
@behzadnouri
Copy link
Contributor

Backporting this PR because turbine over QUIC is shipped in v1.17 but without this patch it will not work properly.

@codecov
Copy link

codecov bot commented Oct 19, 2023

Codecov Report

Merging #33772 (e51f747) into v1.17 (ab99086) will increase coverage by 0.0%.
Report is 1 commits behind head on v1.17.
The diff coverage is 89.1%.

@@           Coverage Diff           @@
##            v1.17   #33772   +/-   ##
=======================================
  Coverage    81.7%    81.7%           
=======================================
  Files         804      804           
  Lines      218154   218178   +24     
=======================================
+ Hits       178404   178424   +20     
- Misses      39750    39754    +4     

@behzadnouri behzadnouri merged commit de407ad into v1.17 Oct 20, 2023
31 checks passed
@behzadnouri behzadnouri deleted the mergify/bp/v1.17/pr-33599 branch October 20, 2023 20:48
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