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.

Sign up for GitHub

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

Jump to bottom

Storage client should prioritize node(s) specified in storage receipts #3354

Closed
kostko opened this issue Oct 1, 2020 · 0 comments · Fixed by #3357
Closed

Storage client should prioritize node(s) specified in storage receipts #3354

kostko opened this issue Oct 1, 2020 · 0 comments · Fixed by #3357
Assignees
@kostko
Labels
c:performance Category: performance c:runtime/compute Category: runtime compute worker c:storage Category: storage

Comments

@kostko
Copy link
Member

kostko commented Oct 1, 2020

Currently the executor tries to fetch storage from any committee node. Instead of doing this blindly, it should prioritize by fetching from storage nodes specified in the storage receipt as those are the ones that should have the given root. The prioritized node identifiers could be hinted by setting a context key.

Related to #1815.
@kostko kostko added c:runtime/compute Category: runtime compute worker c:storage Category: storage c:performance Category: performance labels Oct 1, 2020
@kostko kostko self-assigned this Oct 1, 2020
@kostko kostko mentioned this issue Oct 1, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kostko kostko

Labels
c:performance Category: performance c:runtime/compute Category: runtime compute worker c:storage Category: storage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Prioritize nodes that signed storage receipts oasisprotocol/oasis-core
1 participant
@kostko