Updated on September 24, 2020
Limiting peers reduces the bandwidth used by Hyperledger Besu. Limiting peers also reduces the CPU time and disk access used to manage and respond to peers.
To reduce the maximum number of peers, use the
--max-peers option. The default is 25.
To disable P2P peer discovery, use the
With discovery disabled, peers that have already discovered or are otherwise configured to connect
to the local node (for example, using
admin_addPeer) can open connections.
Static nodes can also open connections.
Monitoring peer connections
JSON-RPC API methods to monitor peer connections include:
The default logging configuration does not list node connection and disconnection messages.
To enable listing of node connection and disconnection messages, specify the
--logging=DEBUG. For more
The console logs connection and disconnection events when the log level is
DEBUG or higher. If
Successfully accepted connection from ... displays, connections are getting through
Sample log output
2018-10-16 12:37:35.479-04:00 | nioEventLoopGroup-3-1 | INFO | NettyP2PNetwork | Successfully accepted connection from 0xa979fb575495b8d6db44f750317d0f4622bf4c2aa3365d6af7c284339968eef29b69ad0dce72a4d8db5ebb4968de0e3bec910127f134779fbcb0cb6d3331163c
Limiting remote connections
In private networks with a level of trust between peers, enabling the remote connection limits is unnecessary and disabling might increase the speed at which nodes can join the network.