You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the documention https://www.consul.io/docs/commands/join.html I believe we should be able to provide mulitple IPs to our server cluster. If it fails to connect to one of the IPs it goes to the next in the list. Currently we are not seeing this.
Example Command: consul -start -c consul --exec /usr/local/bin/consul --agent -config-dir=/etc/consul.d -bind={BIND_IP} -join 10.0.0.1 10.0.0.2 10.0.0.3 -data-dir=/srv/consul -dc=my_test
consul.log
Starting Consul agent...
==> Starting Consul agent RPC...
==> Joining cluster...
==> dial tcp 10.0.0.1:8301: getsockopt: connection refused
I don't see it try any other IPs in the list.
I have three nodes in my server cluster. To simulate the issue i shutdown the consul server process on the first IP in the list.
The text was updated successfully, but these errors were encountered:
I found out after looking into the code and rereading the -join option the way i have the command won't work. Looks like it should be consul -start -c consul --exec /usr/local/bin/consul --agent -config-dir=/etc/consul.d -bind={BIND_IP} -join 10.0.0.1 -join 10.0.0.2 -join 10.0.0.3 -data-dir=/srv/consul -dc=my_test
Consul v0.6.0
Per the documention https://www.consul.io/docs/commands/join.html I believe we should be able to provide mulitple IPs to our server cluster. If it fails to connect to one of the IPs it goes to the next in the list. Currently we are not seeing this.
Example Command:
consul -start -c consul --exec /usr/local/bin/consul --agent -config-dir=/etc/consul.d -bind={BIND_IP} -join 10.0.0.1 10.0.0.2 10.0.0.3 -data-dir=/srv/consul -dc=my_test
consul.log
Starting Consul agent...
==> Starting Consul agent RPC...
==> Joining cluster...
==> dial tcp 10.0.0.1:8301: getsockopt: connection refused
I don't see it try any other IPs in the list.
I have three nodes in my server cluster. To simulate the issue i shutdown the consul server process on the first IP in the list.
The text was updated successfully, but these errors were encountered: