-
Notifications
You must be signed in to change notification settings - Fork 841
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
Deprecate --Xp2p-peer-lower-bound #6501
Conversation
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
|
although it's early access, this option is mentioned in the docs so that needs to be updated eg https://besu.hyperledger.org/public-networks/how-to/connect/manage-peers#limit-peers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm using this option per the documentation at https://besu.hyperledger.org/24.1.0/public-networks/how-to/connect/manage-peers#limit-peers to balance my incoming/outgoing connections to 50:50 after significantly reducing my number of peers. If this option is removed most/all my connections will be outgoing and I will be a net-burden to the network. |
Hi @arnili - I recommend you look at https://besu.hyperledger.org/public-networks/how-to/connect/manage-peers#limit-remote-connections and also static nodes configuration might be a good option for you if you want to maintain connections to specific nodes. Additionally, whether connections are initiated inbound or outbound makes no difference, once the nodes are connected as peers they are treated equally. If you have questions still - reach out in discord! |
Deprecate CLI option --Xp2p-peer-lower-bound and remove usage
Fixes #6376