V2
Ask or search…
K

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
Boost v2.1.0 supports connecting multiple miners to a single LID instance. 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.
  1. 1.
    Pull the new stable release v2.1.0 or RC candidate v2.1.0-rcx
  2. 2.
    Rebuild the binaries with the new version
  3. 3.
    Stop booster-http, booster-bitswap, boostd and boostd-data in that order
  4. 4.
    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
The PGX driver from Yugabyte supports cluster aware Postgres connection out of the box. If you are deploying a multi-node YugabyteDB cluster, then please update your connect-string to use a cluster aware connection.
With Cluster Mode: "postgresql://postgres:[email protected]:5433?load_balance=true"
With Cluster Mode + No SSL: "postgresql://postgres:[email protected]:5433?sslmode=disable&load_balance=true"
  1. 5.
    Once boostd-data service starts, it will throw the below error and quit the process
The database needs to be migrated. Run `boostd-data run yugabyte-migrate`
  1. 6.
    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.
  2. 7.
    Run the one time migration.
boostd-data run yugabyte-migrate --hosts <HOSTS> --connect-string <CONNECT-STRING> --miner-address <MinerID of connected miner>
Please ensure to use the minerID of already connected miner. Other miners can only be connected once the migration is complete.
  1. 8.
    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.
  2. 9.
    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.
  3. 10.
    Start booster-http and booster-bitswap services.
  4. 11.
    If you wish to connected other miners to the upgraded LID service, then please follow the migration guide for each miner.