Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

v1.17: separates out routing repair requests from establishing connections (backport of #33742) #33769

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 #33742 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

…33742)

Currently each outgoing repair request 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 7aa0fae)
@behzadnouri
Copy link
Contributor

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

@behzadnouri behzadnouri added the automerge Merge this Pull Request automatically once CI passes label Oct 19, 2023
@codecov
Copy link

codecov bot commented Oct 19, 2023

Codecov Report

Merging #33769 (56b128f) into v1.17 (ab99086) will decrease coverage by 0.1%.
The diff coverage is 89.4%.

@@            Coverage Diff            @@
##            v1.17   #33769     +/-   ##
=========================================
- Coverage    81.7%    81.7%   -0.1%     
=========================================
  Files         804      804             
  Lines      218154   218198     +44     
=========================================
+ Hits       178404   178418     +14     
- Misses      39750    39780     +30     

@mergify mergify bot merged commit ae1bfff into v1.17 Oct 20, 2023
@mergify mergify bot deleted the mergify/bp/v1.17/pr-33742 branch October 20, 2023 19:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
automerge Merge this Pull Request automatically once CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants