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

Cache peers #1374

Closed
rotilho opened this issue Nov 10, 2018 · 1 comment

Comments

Projects
3 participants
@rotilho
Copy link

commented Nov 10, 2018

It would be nice to the node cache all peers when certain threshold is reached.

This would speed up peer discovery in case of restart and would remove the dependence to the DNS after first execution.

More details:

  • When the threshold is reached all peers are cached in the database
  • Every X seconds the cache is replaced with current peer list
  • If the number of peer is below threshold cache is not updated anymore
  • After start up node sends handshake to all cached peers

@rkeene rkeene added this to the V18.0 milestone Nov 20, 2018

@rkeene rkeene self-assigned this Nov 20, 2018

@zhyatt zhyatt added this to Unscheduled in V18 Dec 27, 2018

@rkeene rkeene moved this from Unscheduled to CP 2 (2018-01-16) in V18 Dec 31, 2018

@zhyatt zhyatt assigned wezrule and unassigned rkeene Jan 7, 2019

@zhyatt zhyatt moved this from CP 2 (2018-01-16) to Unscheduled in V18 Jan 7, 2019

@wezrule wezrule moved this from Unscheduled to CP 2 (2018-01-16) in V18 Jan 10, 2019

@zhyatt zhyatt moved this from CP 2 (2018-01-16) to CP 3 (2018-01-23) in V18 Jan 26, 2019

@wezrule

This comment has been minimized.

Copy link
Collaborator

commented Jan 30, 2019

This has been solved by #1608

@wezrule wezrule closed this Jan 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.