LogoLogo
v2.x (Stable)
v2.x (Stable)
  • What is Boost?
  • Features
  • Components
    • boostd
      • Repository
      • GraphQL API
      • JSON-RPC API
      • SQLite metadata database
    • Local Index Directory
      • Index types
      • Dependencies
      • Initialisation
    • boostd-data
    • YugabyteDB
    • booster-http
    • booster-bitswap
    • libp2p Protocols
  • Hardware requirements
    • YugabyteDB
  • Installation
  • New Boost Setup
  • Configuration
    • UI Settings
    • HTTP Transfer limit
    • Deal Filters
    • Remote CommP
    • Legacy Deal configuration
    • HTTP indexer announcement
    • Manual Publish Storage Deal Message
  • Monitoring
    • Setting up a monitoring stack for Boost
  • Storing data on Filecoin
  • Retrieving data from Filecoin
    • HTTP retrieval
    • Advanced Configuration of booster-http
    • Bitswap retrieval
  • Backup and Restore
  • Tutorials
    • How to upgrade from Boost v1 to Boost v2
    • How to re-index unsealed pieces that are flagged by LID in Boost v2
    • How to upgrade from v2.0.0 to v2.1.0
    • How to upgrade from v2.1.x to v2.2.0
    • Start and stop Boost processes
    • How to store files with Boost on Filecoin
    • Using filters for storage and retrieval deals
    • Migrate from Lotus to Boost
    • How to onboard data using DDO deals
  • Troubleshooting
  • Experimental Features
    • FVM Contract Deals
    • Direct Deals
    • Data Segment Indexing
  • FAQ
  • Need help?
Powered by GitBook
On this page
  • Start
  • Stop
Edit on GitHub
Export as PDF
  1. Tutorials

Start and stop Boost processes

This pages describes the order in which different boost processes must be started and stopped

Start

  1. Start YugabyteDB and wait for services to come online.

  2. Start boostd-data process.

  3. Start boostd process.

  4. Start booster-http and booster-bitswap processes.

Stop

  1. Stop booster-http and booster-bitswap processes.

  2. Stop boostd process.

  3. Stop boostd-data process.

  4. Finally, you can stop YugabyteDB services.

YugabyteDB services are not required to be stopped if your maintenance work does not directly make changes to the DB itself. The DB can simply be disconnected from boost process by shutting down the boostd-data process.

PreviousHow to upgrade from v2.1.x to v2.2.0NextHow to store files with Boost on Filecoin

Last updated 1 year ago