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

Fall back to Cloud Auto Join when there are no healthy servers #5516

Open
dadgar opened this issue Mar 20, 2019 · 1 comment
Open

Fall back to Cloud Auto Join when there are no healthy servers #5516

dadgar opened this issue Mar 20, 2019 · 1 comment
Assignees
Labels
type/enhancement Proposed improvement or new feature

Comments

@dadgar
Copy link
Contributor

dadgar commented Mar 20, 2019

Feature Description

If a Consul agent detects that there are no healthy servers or it has failed to RPC to any of the servers in its list, it should search for new servers via the cloud auto-join/retry join mechanism.

Use Case(s)

This can solve the scenario in which the set of servers is restarted with new IPs and thus is not a part of the Serf LAN group.

@pearkes pearkes added the type/enhancement Proposed improvement or new feature label Mar 20, 2019
@zlepper
Copy link

zlepper commented Sep 22, 2019

Another case for this: Azure scale sets for some reason stats a lot of servers, before it scales down. If Consul manages to start before the servers are removed again, it might have references to dead servers, which then prevents anything from working. The only workaround i have found is connecting the servers, removing the data directory, and restarting consul, which is not really a scaleable solution in the long term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

4 participants