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

bootnodes vs static nodes - add to explanation #1461

Closed
macfarla opened this issue Nov 29, 2023 · 1 comment · Fixed by #1463
Closed

bootnodes vs static nodes - add to explanation #1461

macfarla opened this issue Nov 29, 2023 · 1 comment · Fixed by #1463
Assignees

Comments

@macfarla
Copy link
Contributor

https://besu.hyperledger.org/development/public-networks/how-to/connect/static-nodes

Suggest to expand the note on this page to highlight the important difference between bootnodes and static nodes -

Static nodes and bootnodes are only treated the same at startup (ie besu tries to connect to them all). However only static nodes (and enodes added via admin_addPeer) are included in "maintained peers" (to which besu regularly attempts to reconnect), not bootnodes. So if you only have bootnodes, after startup you're relying solely on discovery. So in small node networks, we would recommend static nodes (or both) to mitigate low peer count issues.

@MadelineMurray
Copy link
Contributor

@bgravenorst - can you assign this one to me please

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 a pull request may close this issue.

2 participants