Skip to content
You are reading Hyperledger Besu development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.
Last update: April 1, 2021

Managing peers

Limiting peers

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.

No discovery

To disable P2P discovery, use the --discovery-enabled option.

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:

Each peer entry returned by admin_peers includes a protocols section. Use the information in the protocols section to:

  • Determine health of peers. For example, an external process could use admin_peers and admin_removePeer to disconnect from peers that are stalled at a single difficulty for an extended period of time.

  • Monitor node health. For example, if peers are reporting increasing difficulties but node is stuck at the same block number, the node may be on a different fork to most peers.

  • Determine which protocol level peers are communicating with. For example, to see if "version": 65 is being used to reduce transaction sharing traffic.

Node connections

The default logging configuration does not list node connection and disconnection messages.

To enable listing of node connection and disconnection messages, specify the --logging option --logging=DEBUG. For more verbosity, specify --logging=TRACE.

The console logs connection and disconnection events when the log level is DEBUG or higher. If the message Successfully accepted connection from ... displays, connections are getting through the firewalls.

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 might adversely affect the speed at which nodes can join the network. Limiting remote connections may cause a clique of nodes to form when the number of nodes in the network is slightly higher than --max-peers. The nodes in this clique are all connected to each other and cannot accept more connections.

In public networks, enabling the remote connections limit is necessary to prevent eclipse attacks, especially when using --sync-mode and --fast-sync-min-peers.

Questions or feedback? You can discuss issues and obtain free support on Hyperledger Besu chat channel.
For Hyperledger Besu community support, contact the mailing list besu@lists.hyperledger.org