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

Do not truncate the list of peers for propagation #1738

Merged
merged 1 commit into from
Feb 6, 2020

Conversation

mzabaluev
Copy link
Contributor

The vector obtained from Topology::view is sorted by node ID, so truncations make the network biased toward nodes with low IDs.
Let the client connections rotate "naturally", allowing some churn.
A limit on the view size should be implemented in Poldercast:
primetype/poldercast#6

@mzabaluev mzabaluev added the subsys-network network related label Feb 6, 2020
@mzabaluev mzabaluev added this to the Net improvement 4 milestone Feb 6, 2020
@mzabaluev mzabaluev requested a review from rinor February 6, 2020 10:17
The vector obtained from Topology::view is sorted by node ID,
so truncations make the network biased toward nodes with low IDs.
Let the client connections rotate "naturally", allowing some churn.
A limit on the view size should be implemented in Poldercast:
primetype/poldercast#6
@mzabaluev mzabaluev force-pushed the no-topology-view-truncation branch from 11bba01 to 7608a33 Compare February 6, 2020 10:48
@mzabaluev mzabaluev merged commit 222ee4a into master Feb 6, 2020
@mzabaluev mzabaluev deleted the no-topology-view-truncation branch February 6, 2020 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subsys-network network related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants