81ba6ab6f0
* feat: lp mig - first few steps * lp mig: default tasks * code comments * docs * lp-mig-progress * shared * comments and todos * fix: curio: rename lotus-provider to curio (#11645) * rename provider to curio * install gotext * fix lint errors, mod tidy * fix typo * fix API_INFO and add gotext to circleCI * add back gotext * add gotext after remerge * lp: channels doc * finish easy-migration TODOs * out generate * merging and more renames * avoid make-all * minor doc stuff * cu: make gen * make gen fix * make gen * tryfix * go mod tidy * minor ez migration fixes * ez setup - ui cleanups * better error message * guided setup colors * better path to saveconfigtolayer * loadconfigwithupgrades fix * readMiner oops * guided - homedir * err if miner is running * prompt error should exit * process already running, miner_id sectors in migration * dont prompt for language a second time * check miner stopped * unlock repo * render and sql oops * curio easyMig - some fixes * easyMigration runs successfully * lint * review fixes * fix backup path * fixes1 * fixes2 * fixes 3 --------- Co-authored-by: LexLuthr <88259624+LexLuthr@users.noreply.github.com> Co-authored-by: LexLuthr <lexluthr@protocol.ai>
29 lines
1012 B
Markdown
29 lines
1012 B
Markdown
# Lotus-Provider Sealer
|
|
|
|
## Overview
|
|
|
|
The lotus-provider sealer is a collection of harmony tasks and a common poller
|
|
which implement the sealing functionality of the Filecoin protocol.
|
|
|
|
## Pipeline Tasks
|
|
|
|
* SDR pipeline
|
|
* `SDR` - Generate SDR layers
|
|
* `SDRTrees` - Generate tree files (TreeD, TreeR, TreeC)
|
|
* `PreCommitSubmit` - Submit precommit message to the network
|
|
* `PoRep` - Generate PoRep proof
|
|
* `CommitSubmit` - Submit commit message to the network
|
|
|
|
# Poller
|
|
|
|
The poller is a background process running on every node which runs any of the
|
|
SDR pipeline tasks. It periodically checks the state of sectors in the SDR pipeline
|
|
and schedules any tasks to run which will move the sector along the pipeline.
|
|
|
|
# Error Handling
|
|
|
|
* Pipeline tasks are expected to always finish successfully as harmonytask tasks.
|
|
If a sealing task encounters an error, it should mark the sector pipeline entry
|
|
as failed and exit without erroring. The poller will then figure out a recovery
|
|
strategy for the sector.
|