Upgrading your Network
- Using an orchestration method (for example, Ansible or Chef) to keep all nodes in sync with your desired configuration.
- Storing your configuration under version control.
The Ansible role on Galaxy can be used directly or customised to suit your needs. Upgrade by running the play. The play:
Upgrade the Besu version on nodes by running the play with the new version. For details, see the Readme on Galaxy. The play:
- Stops Besu.
- Downloads the updated version.
- Applies any new configuration.
- Starts Besu.
Finding Peers on Restarting
Nodes store known peers in the peer table. The peer table is not persisted to disk. When a node restarts, the node connects to the specified bootnodes and discover other nodes through the peer discovery process. The node continues collecting data from where it was (assuming there was no data corruption in a failure scenario).
Before the node was restarted, connected peers saved the node details in their peer tables. These peers may reconnect to the restarted node. The restarted node uses these peers as well as the bootnodes to discover more peers. To ensure that the restarted node successfully rejoins the network ensure at least one operational bootnode is specified.