Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Merged by Bors] - fetch: smarter peer selection #6477
[Merged by Bors] - fetch: smarter peer selection #6477
Changes from all commits
6dde162
f368542
8ad95ee
fad6531
8b3ffa9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 307 in fetch/fetch.go
Codecov / codecov/patch
fetch/fetch.go#L304-L307
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not fully understanding this - why only at least one protocol needs to be supported? The only place outside of tests where this is used
activeSetProtocol
andhashProtocol
are requested, aren't both needed?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is that there may be multiple versions of
syncv2
protocol deployed at some point in time:sync/2
,sync/2.1
and so on. When choosing peers for multipeer sync, any of such nodes will do, it's just that different protocols will be in use, later versions being more traffic-efficient etc.For the purpose of hash fetching, the requirement may be just one of
activeSetProtocol
/hashProtocol
or all of them, depending on which IDs are being fetched. It maybe could make some sense to invent a more complex logic for paritioning the set of hashes to download by the protocol etc., but in practice the servers foractiveSetProtocol
andhashProtocol
are enabled almost at the same instant at the end of the node initialization, and in a very unlikely case of a race the worst thing that may happen is currentgo-spacemesh
behavior, that is, failed fetch which will be retried later, with failed peer getting lower priority when doing peer selection. So, in case of hash fetching, from practical standpoint it doesn't really matter whether we passactiveSetProtocol
,hashProtocol
or both to this function.