Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

Max Limit Peers #96

Open
ccamaleon5 opened this issue Sep 29, 2020 · 2 comments
Open

Max Limit Peers #96

ccamaleon5 opened this issue Sep 29, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@ccamaleon5
Copy link
Collaborator

Problem

When the node reaches the maximum connection limit (by default 25), it begins to disconnect. This affects performance while the node is disconnecting from the other peers.

Solution

Our recommendation for these cases is to limit connections only to bootnodes, which can be achieved as follows:
In the start-pantheon.sh file located in the / lacchain folder add the flag
--permissions-nodes-config-file-enabled

With which the file would look like this:

#! / bin / bash
LOG4J_CONFIGURATION_FILE=/root/lacchain/log.xml pantheon --data-path /root/lacchain/data --genesis-file=/root/lacchain/data/genesis.json --network-id 648529 --permissions-nodes- config-file-enabled --permissions-nodes-contract-enabled --permissions-nodes-contract-address=0x0000000000000000000000000000000000009999 --config-file=/root/lacchain/config.toml

Additionally in the permissions_config.toml file located in the /lacchain/data folder add the bootnodes located in config.toml
´ nodes-whitelist = [ bootnodes list from config.toml ]´

Finally restart the besu service
service pantheon restart

@ccamaleon5 ccamaleon5 added the enhancement New feature or request label Sep 29, 2020
@ccamaleon5
Copy link
Collaborator Author

Smart contracts will be created to limit the connection between the different nodes.

@davux
Copy link
Member

davux commented Oct 1, 2020

Maybe this should be reported upstream.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants