Configurable limit needed for number of nodes returned in a view #6
Comments
mzabaluev
pushed a commit
to input-output-hk/jormungandr
that referenced
this issue
Feb 6, 2020
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
pushed a commit
to input-output-hk/jormungandr
that referenced
this issue
Feb 6, 2020
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the application has a limit on the number of simultaneous P2P connections it wants to run, it does not make sense to return more nodes from the topology view. Conversely, if the application can afford more connections, the topology modules might be able to provide more nodes.
The text was updated successfully, but these errors were encountered: