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

Clarify what happens when no bootnodes are specified. #1477

Merged
merged 7 commits into from
Jan 9, 2024
Merged

Clarify what happens when no bootnodes are specified. #1477

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
998c233
Add bootnode clarification in case of no bootnodes
Gabriel-Trintinalia Jan 8, 2024
aa12306
Add bootnode clarification in case of no bootnodes
Gabriel-Trintinalia Jan 8, 2024
d1e883c
Add bootnode clarification in case of no bootnodes
Gabriel-Trintinalia Jan 8, 2024
ad51b4e
Update versioned_docs/version-23.10.3/private-networks/how-to/configu…
Gabriel-Trintinalia Jan 8, 2024
3dbe9a1
Merge branch 'main' into add-bootnode-observation
alexandratran Jan 8, 2024
a5039d9
Fix file change
Gabriel-Trintinalia Jan 8, 2024
513a2fd
Merge main into branch
Gabriel-Trintinalia Jan 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/private-networks/how-to/configure/bootnodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ By default, peer discovery listens on all available network interfaces. If the d

## Configure bootnodes in a production network

A network must have at least one operating bootnode. To allow for continuity in the event of failure, configure two or more bootnodes in a production network.
A network must have at least one operating bootnode. To allow for continuity in the event of failure, configure two or more bootnodes in a production network. If you don't configure any bootnodes, Besu uses Mainnet's default bootnodes.

We don't recommend putting bootnodes behind a load balancer because the [enode](../../../public-networks/concepts/node-keys.md#enode-url) relates to the node public key, IP address, and discovery ports. Any changes to a bootnode enode prevents other nodes from being able to establish a connection with the bootnode. This is why we recommend putting more bootnodes on the network itself.

Expand Down