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.

Sign up for GitHub

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

Jump to bottom

Short lived relay connections in low latency deployments #1420

Closed
corverroos opened this issue Nov 10, 2022 · 0 comments
Closed

Short lived relay connections in low latency deployments #1420

corverroos opened this issue Nov 10, 2022 · 0 comments
Assignees
@corverroos

Comments

@corverroos
Copy link
Contributor

🐞 Bug Report

Description

Relay connections are short lived in deployments with low latency. This creates flapping "insufficient peer" status as there are frequent instances of F+1 relay connection that are "busy connecting", ie "no active connection". This could also have an impact on other metrics since p2p sender has frequent "stream reset errors".
This was referenced Nov 10, 2022
Merged
Merged
obol-bulldozer bot pushed a commit that referenced this issue Nov 10, 2022
@corverroos
cmd: increase bootnode connection data limit (#1419)
a485cb2 
Increase bootnode libp2p relay connection limits from default 128kB to 2MB as the default is very small.

category: misc
ticket: #1420
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@corverroos corverroos

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@corverroos