You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: This issue originally started out as Investigaton of storing tree_r_last in Lotus-Miner to see how we could make unsealing better, which lead us to a longer path of unsealing enhancements after discussions with the proofs-team. This issue ticket has therefore been repurposed reflect that epic.
User story:
As a storage provider (SP) who stores sealed sectors, I need an efficient and reliable unsealing process which does not require manual work to attach workers to where the sealed sector is located, allowing me to focus on handling large volume of sealed sectors being unsealed for clients.
Acceptence criteria:
Unsealing of every sector type (Deals, SnapDeal) functions without bugs.
The unsealing process should not require manual intervention for unsealing to work on unsealing-workers; such as attaching the location where the sealed sector is stored to a worker.
Techincal scope
The content you are editing has changed. Please copy your edits and refresh the page.
Closing this issue now that #11011 has been merged, and is on its way to users with the Lotus v1.23.4 release train.
The linked PR introduces significant improvements and bugfixes with regards to unsealing, and ensures that unsealing operates as anticipated. Consequently, the unsealing of deal sectors, Snap-sectors without sector keys, and Snap-sectors with sector keys now all function seamlessly.
Additional improvements/bugfixes with this PR includes:
Enabling unsealing on workers with only sealing paths. 🎉
Transferring unsealed files to long-term storage upon successful unsealing. ➡️
Ensuring no residual files in sealing paths post a successful unsealing operation. 🧹
User story:
As a storage provider (SP) who stores sealed sectors, I need an efficient and reliable unsealing process which does not require manual work to attach workers to where the sealed sector is located, allowing me to focus on handling large volume of sealed sectors being unsealed for clients.
Acceptence criteria:
Techincal scope
Tasks
sealed
file in precommit1 rust-fil-proofs#1665Point estimation:
The text was updated successfully, but these errors were encountered: