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
calls try_lock endpoint <- the files are initialized
download/challenge
upload/response
try_contribute <- the files are written to
As you can see, we have several requests before creating and using the files. And if the contributor or coordinator is stopped in between of these calls, there's a high chance to obtain incorrect state in the transcript.
What if we move the file initialization from try_lock to try_contribute? As a result, the files will be created right before being used, and it will reduce the window in which it's possible to obtain incorrect state by a lot.
If the contributor goes down, it will not affect the files at all, so we'll have to take care only about coordinator restarts.
The text was updated successfully, but these errors were encountered:
Contributor works like this:
try_lock
endpoint <- the files are initializeddownload/challenge
upload/response
try_contribute
<- the files are written toAs you can see, we have several requests before creating and using the files. And if the contributor or coordinator is stopped in between of these calls, there's a high chance to obtain incorrect state in the transcript.
What if we move the file initialization from
try_lock
totry_contribute
? As a result, the files will be created right before being used, and it will reduce the window in which it's possible to obtain incorrect state by a lot.If the contributor goes down, it will not affect the files at all, so we'll have to take care only about coordinator restarts.
The text was updated successfully, but these errors were encountered: