-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
server: join semantics are not exposed via configuration #180
Comments
@macb this was probably just an oversight for the servers. In Nomad the client's don't need to join the gossip pool, so only the server nodes should need these options. We should add them, though. Thanks! |
I am really appreciative for the flexibility and simplicity inherent in Consul's leader election, and the lack of the same semantics in Nomad makes deploying Nomad leaders to AWS auto-scaling groups much more difficult than Consul. (I would welcome any suggestions - in case I am missing something obvious). To be more clear: the current setup with Consul makes it possible to easily give Consul an arbitrary list of IPs, and set it up to continually retry/reload/restart until Consul succeeds to elect a leader. There is a bit of a discussion on these topic on the list: https://groups.google.com/d/msg/nomad-tool/PXH0rQK_7sM/zQMP3mRIDwAJ |
+1 |
#527 addresses this! |
\o/ |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Similar to how consul offers flags and config file to have a server join the cluster
nomad
doesn't. Was this an intended deviation?The text was updated successfully, but these errors were encountered: