Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

removeTask is it necessary? #39

Closed
badb opened this issue Nov 26, 2015 · 0 comments
Closed

removeTask is it necessary? #39

badb opened this issue Nov 26, 2015 · 0 comments

Comments

@badb
Copy link
Contributor

badb commented Nov 26, 2015

It's quite obvious that user should be allowed to cancel computation, ie. paid for previously computed subtasks, but don't accept any other providers issue.
What is not clear is that if there should be special broadcast method indicating that requester doesn't want to compute this task anymore and information about it shouldn't been kept and broadcast further. It may be useful for very long-standing task but generates some additional complexity.

Additional note: we should be sure that when requester decides to cancel task it pays for all remaining computation, ie. results for the subtasks that has already started being computed. Additional question: what should happened when we added redundant computation and some subtasks has been computed by some nodes but not enough to verify them.

@badb badb added the question label Nov 26, 2015
@chfast chfast added the planned label Apr 6, 2016
@badb badb added this to the Brass 0.4 milestone May 22, 2016
@badb badb removed the planned label Jul 12, 2016
@badb badb closed this as completed Jan 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants