Commits on Aug 16, 2021

1. switch deal-making to dagstore + carv2. …

   This commit removes badger from the deal-making processes, and
   moves to a new architecture with the dagstore as the cental
   component on the miner-side, and CARv2s on the client-side.
   
   Every deal that has been handed off to the sealing subsystem becomes
   a shard in the dagstore. Shards are mounted via the LotusMount, which
   teaches the dagstore how to load the related piece when serving
   retrievals.
   
   When the miner starts the Lotus for the first time with this patch,
   we will perform a one-time migration of all active deals into the
   dagstore. This is a lightweight process, and it consists simply
   of registering the shards in the dagstore.
   
   Shards are backed by the unsealed copy of the piece. This is currently
   a CARv1. However, the dagstore keeps CARv2 indices for all pieces, so
   when it's time to acquire a shard to serve a retrieval, the unsealed
   CARv1 is joined with its index (safeguarded by the dagstore), to form
   a read-only blockstore, thus taking the place of the monolithic
   badger.
   
   Data transfers have been adjusted to interface directly with CARv2 files.
   On inbound transfers (client retrievals, miner storage deals), we stream
   the received data into a CARv2 ReadWrite blockstore. On outbound transfers
   (client storage deals, miner retrievals), we serve the data off a CARv2
   ReadOnly blockstore.
   
   Client-side imports are managed by the refactored *imports.Manager
   component (when not using IPFS integration). Just like it before, we use
   the go-filestore library to avoid duplicating the data from the original
   file in the resulting UnixFS DAG (concretely the leaves). However, the
   target of those imports are what we call "ref-CARv2s": CARv2 files placed
   under the `$LOTUS_PATH/imports` directory, containing the intermediate
   nodes in full, and the leaves as positional references to the original file
   on disk.
   
   Client-side retrievals are placed into CARv2 files in the location:
   `$LOTUS_PATH/retrievals`.
   
   A new set of `Dagstore*` JSON-RPC operations and `lotus-miner dagstore`
   subcommands have been introduced on the miner-side to inspect and manage
   the dagstore.
   
   Despite moving to a CARv2-backed system, the IPFS integration has been
   respected, and it continues to be possible to make storage deals with data
   held in an IPFS node, and to perform retrievals directly into an IPFS node.
   
   NOTE: because the "staging" and "client" Badger blockstores are no longer
   used, existing imports on the client will be rendered useless. On startup,
   Lotus will enumerate all imports and print WARN statements on the log for
   each import that needs to be reimported. These log lines contain these
   messages:
   
   - import lacks carv2 path; import will not work; please reimport
   - import has missing/broken carv2; please reimport
   
   At the end, we will print a "sanity check completed" message indicating
   the count of imports found, and how many were deemed broken.
   
   Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com>
   Co-authored-by: Dirk McCormick <dirkmdev@gmail.com>

   

   3 people committed Aug 16, 2021
   Configuration menu

   • View commit details
   • Copy full SHA for 9d9fd9d
   • Browse repository at this point

   Copy the full SHA

   9d9fd9d View commit details

   Browse the repository at this point in the history