How to upgrade from v2.0.0 to v2.1.0
This is a step by step guide to upgrade from Boost v2.0.0 to Boost v2.1.0
Last updated
This is a step by step guide to upgrade from Boost v2.0.0 to Boost v2.1.0
Last updated
Boost v2.1.0 supports . This would enable the SP to serve retrievals from all the connected miners via a single boostd
, booster-bitswap
or booster-http
instance. To enable this feature, we need to update our existing LID tables to add minerID to the piece metadata.
Pull the new stable release v2.1.0 or RC candidate v2.1.0-rcx
Rebuild the binaries with the new version
Stop booster-http
, booster-bitswap
, boostd
and boostd-data
in that order
Start boostd-data
service first. If you are using systemd service files to manage the process, then please start it manually without using the systemd files.
The Postgres <CONNECT_STRING> will need to be updated to not use SSL mode. Otherwise, you might see error connecting to the DB. The updated connect string should like below
postgresql://<username>:<password>@<yugabytedb>:5433?sslmode=disable
Once boostd-data
service starts, it will throw the below error and quit the process
If you do not see the above error and process does not exit, then you do not require a migration. At this point, please skip to step 9.
Run the one time migration.
Once the migration is finished (few seconds to 2 minutes), SPs using systemd to maintain boostd-data
service should also update their connect-string
in the systemd service files.
Start the boostd-data
process (or service) and start your boostd
instance. Go to the UI and confirm that you can see your minerID on the top left side of the page and the LID page is being populated correctly.
Start booster-http
and booster-bitswap
services.
If you wish to connected other miners to the upgraded LID service, then please follow the .