Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

storage/client: Only wait for F+1 successful writes #1821

Closed
tjanez opened this issue Jun 14, 2019 · 0 comments · Fixed by #3021
Closed

storage/client: Only wait for F+1 successful writes #1821

tjanez opened this issue Jun 14, 2019 · 0 comments · Fixed by #3021
Assignees
Labels
c:roothash Category: root hash service c:storage Category: storage

Comments

@tjanez
Copy link
Member

tjanez commented Jun 14, 2019

After #1792 is merged, the storage client will utilize all the nodes from the storage committee.

However, when writing to nodes, it will wait for all the nodes to finish. We should implement only waiting for F+1 nodes, where F is a consensus parameter that needs to be checked by BFT roothash (as otherwise some compute nodes could commit to less than F+1 nodes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:roothash Category: root hash service c:storage Category: storage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants