-
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
retry_join (inside server_join) does not support go-sockaddr syntax #8169
Comments
Any reason why the syntax has not been supported (originally) in Nomad's Having this greatly helps to setup a single node |
@shantanugadgil I saw your comment in #10404 and it raised questions for me. I've never seen a case where a Nomad agent running in client and server mode did not join itself properly in the absence of a join configuration. Could you perhaps share more about your configuration? I'm unclear as to why you'd need a join configuration at all. |
@angrycub following are my configuration files:
Are you suggesting that the Let me try commenting it out in the EDIT: Please note, the above configuration is actually adapted from the multi node setup, where servers and clients are different, so I am all ears on how to optimize this to remove hard coded IP addresses for single node setups :) |
Nomad version
Nomad v0.11.3 (8918fc8)
Operating system and Environment details
CentOS 8/Ubuntu 18.04/et.al
Issue
Nomad's
retry_join
directive only supports thego-discover
syntax, but does not support thego-sockaddr
syntax.https://www.nomadproject.io/docs/configuration/server_join/#retry_join
Consul's
retry_join
supports bothhttps://www.consul.io/docs/agent/options#_retry_join
Reproduction steps
define a
client
section in the server config and define the client section as:Upon restarting the service, this will keep emitting error messages in the logs about how the
retry_join
parameter is invalidJob file (if appropriate)
n/a
Nomad Client logs (if appropriate)
n/a
Nomad Server logs (if appropriate)
The use case here is of a typical quick one node server/client with minimal tinkering needed to the config file.
The text was updated successfully, but these errors were encountered: