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

[backport] p2p: use decaying tags for fetch peers (#5564) #5568

Merged
merged 1 commit into from
Feb 14, 2024

Conversation

ivan4th
Copy link
Contributor

@ivan4th ivan4th commented Feb 14, 2024

Motivation

Backport #5564

Description

Use decaying tags for fetch peers

When there's some peer churn (connection manager enabled, which is the default), fetch can be interrupted by connection manager dropping connections which are currently used for fetching. This can happen both for fetch clients and servers, breaking sync.
Copy link

codecov bot commented Feb 14, 2024

Codecov Report

Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (1c7a8a9) 77.3% compared to head (e2b9851) 77.3%.
Report is 6 commits behind head on v1.3.

Files Patch % Lines
p2p/server/server.go 71.4% 3 Missing and 3 partials ⚠️
p2p/host.go 50.0% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##            v1.3   #5568     +/-   ##
=======================================
- Coverage   77.3%   77.3%   -0.1%     
=======================================
  Files        261     261             
  Lines      30891   30919     +28     
=======================================
+ Hits       23903   23923     +20     
- Misses      5488    5493      +5     
- Partials    1500    1503      +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ivan4th
Copy link
Contributor Author

ivan4th commented Feb 14, 2024

bors merge

spacemesh-bors bot pushed a commit that referenced this pull request Feb 14, 2024
## Motivation

Backport #5564 

## Description

Use decaying tags for fetch peers
@spacemesh-bors
Copy link

This PR was included in a batch that successfully built, but then failed to merge into v1.3. It will not be retried.

Additional information:

Response status code: 422
{"message":"Changes must be made through a pull request.","documentation_url":"https://docs.github.com/articles/about-protected-branches"}

@ivan4th
Copy link
Contributor Author

ivan4th commented Feb 14, 2024

bors merge

@ivan4th
Copy link
Contributor Author

ivan4th commented Feb 14, 2024

bors cancel

@spacemesh-bors
Copy link

Canceled.

@ivan4th ivan4th merged commit 2c7554b into v1.3 Feb 14, 2024
16 of 18 checks passed
@ivan4th ivan4th deleted the backport-5564 branch February 14, 2024 12:54
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.

None yet

2 participants