This post shows how to update your existing Streamr Broker node to the latest version. If you are installing your node for the first time, please refer to the instructions laid out in the initial blog post.

Updating to the latest version

The update is available for both the NPM and Docker versions of the Broker node software. As before, there are two sets of instructions, depending on whether you originally installed your node with Docker or NPM. Note that there is no need to run the config wizard again.When starting the Broker node for the first time after the update, the configuration is migrated automatically between old and new versions.

Updating a node running on Docker

Stop the currently running Broker as follows:

  • Identify and record the container ID of your node by running docker ps
  • Then, docker stop <container_ID>

Next, pull the latest version of the Broker node software,

docker pull streamr/broker-node:testnet

Then start the container with the same command as before in the previous blog post

After updating, you should see the broker version 29.0.0 or higher when the node is starting.

Updating a node running on NPM

  • Stop your existing broker node process (Ctrl+C for example)
  • Then, npm install -g streamr-broker@testnet
  • After updating, you should see the broker version at 29.0.0 or higher
  • Start the node using the streamr-broker command as usual.

If you have any problems updating with npm, you could try running npm doctor to diagnose the symptoms.

These instructions have been tested on Linux and macOS and may vary on Windows. Our Discord #testnet-troubleshooting and #testnet-faq channels are an excellent resource for help with any obstacles.

What’s new in the update?

Everything has been improved, especially horizontal scalability. We now have the possibility to break out from the boundaries of a single tracker and add as many trackers as needed in order to facilitate larger networks. Additionally we have improved the recovery and robustness around connections in the network. Any bad weather should not affect the network as much as it might have affected it before.