Skip to content
This repository was archived by the owner on Sep 26, 2023. It is now read-only.

FR: The abillity to re-propose deals that have already been proped to a specific miner. #116

Open
marshyonline opened this issue Jul 31, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@marshyonline
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Sometimes things happen and deals break - The ability to reissue specific deals to specific miners I think is a must for large-scale deployments

Describe the solution you'd like
singularity repl create-deal $Repl-ID $CID $Miner etc etc

Describe alternatives you've considered
Manually reissuing deals via scripts, but this is a bandaid for a feature that would make more sense inside the deal-tracking of this application.

@marshyonline marshyonline added the enhancement New feature or request label Jul 31, 2022
@liuziba liuziba assigned kernelogic and unassigned liuziba Jul 31, 2022
@xinaxu
Copy link
Member

xinaxu commented Mar 20, 2023

@marshyonline this isn't really needed. because you can use lotus or boost to send out deal directly to the provider, and it will get picked up by the tracking service anyway.
In fact, if deals break, after the proposal expires, it will be automatically picked up by the replication worker anyway so you don't even need to monitor the deal status and attempt a remedy yourself - this is because the deal tracking service will mark the deal to 'proposal-expired' when the deal is not on chain before the proposal expires. Then this CID will have a chance to get picked up by the replication worker.

@kernelogic
Copy link
Contributor

Right now, if you wait after deal expire, simply re-create a new replication request using the same criteria, or resume the old one, it will resend failed ones and skip the successful ones.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants