-
Notifications
You must be signed in to change notification settings - Fork 662
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
Persist discovered peers #2187
Comments
The purpose of |
That is a purpose. We are also tentatively recommending it in the ops guide as a way of getting maximum reboot resilience in manually configured deployments, to which you responded that we should consider persisting discovered peers instead. |
Yes, I know I said that. I would quite like to know when we are going to forget about a discovered peer. |
btw, the recommendation in the ops guide only works if the peer isn't behind a firewall that blocks inbound connections. It also assumes that operators know the external IP(s). |
I'm just including it for the benefit of those who weren't part of the conversation.
Indeed - thinking about that is part of this issue.
True. Ops guide doesn't consider such deployments yet! |
Actually, I didn't say that. I observed in the ops guide PR that "we'd benefit from |
When you manually add a new peer to an existing network it is not desirable to go back to the existing peers and do
weave connect
(assuming that persists as per #2186) - it would be better if existing peers remembered the new peer automatically.The text was updated successfully, but these errors were encountered: