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

Work with a 'running config' / live env #458

Open
kruisdraad opened this issue Aug 4, 2018 · 0 comments
Open

Work with a 'running config' / live env #458

kruisdraad opened this issue Aug 4, 2018 · 0 comments

Comments

@kruisdraad
Copy link
Contributor

Currently you need to reload the entire system, restarting all peers, routing and create a routing convergence if peers depended on the route. I suggest two things:

  1. signal the peer if this side goes down gracefully (and reconnect using different timers, for a fast reconnect).
  2. create childs and have a main proces that runs, kicking of chils for each plugin. Leave the main process (router) and childs (peerings) running unless something has changed. If there is a change either just add a new peering (its bad to have to restart everything to add something live) or only restart the affected peering child plugin.

This would create a lot more stable connector as if i am looking now, with 8 peers on a node, it takes quite some time. Also each peer seems to be started and connected in a sync way, causing it to take more time ... i dont see why this could not be done async as each peering should not be depending on each other and just collect routes.

@adrianhopebailie adrianhopebailie added this to To do in Connector Refactor via automation Oct 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant