Support multiple -join ips about docker-consul HOT 12 CLOSED

Not initially. You can after it's started using the API. What is the
scenario?

On Wednesday, October 15, 2014, Yaron Rosenbaum [email protected]
wrote:

Hi

Is it possible to -join multiple ips?

—
Reply to this email directly or view it on GitHub
#27.

Jeff Lindsay
http://progrium.com

from docker-consul.

For us it would be a self-assembling cluster where the join IPs are gathered from outside the cluster, such as etcd on coreos. We aim to solve this with sidekick systemd units to do explicit joins using docker exec. A PR may be incoming ;-)

from docker-consul.

hey @justinclayton,
would a fleet systemd file, like so: https://gist.github.com/skippy/94645f8442203dc37b5b
help?

from docker-consul.

+1. Multiple join IPs are useful to increase failure tolerance. Given just one IP, an agent will fail joining the cluster when the target machine is down.

@progrium, here is the scenario: suppose that we have 3 cluster servers: 10.0.0.1, 10.0.0.2 and 10.0.0.3, and 10.0.0.1 is down. The cluster still has the quorum and thus available. New client agents will be able to join the cluster if we provide them with all three join IPs, but will fail given just 10.0.0.1.

from docker-consul.

You all know you can do more joins via the API once it's booted, right?

On Sun, Jan 11, 2015 at 9:42 AM, Семён [email protected] wrote:

+1. Multiple join IPs are useful to increase failure tolerance. Given just
one IP, agent may fail to join the cluster when the target machine is down.

—
Reply to this email directly or view it on GitHub
#27 (comment)
.

Jeff Lindsay
http://progrium.com

from docker-consul.

@progrium yes, that's how we're solving for this. Each consul server has a sidekick unit file that puts its ip into etcd and then periodically does an explicit join of the others that have already done so using docker exec. There's probably a more elegant solution somewhere, but it works for us.

from docker-consul.

@progrium, yes, but specifying multiple join ips when starting a new agent is just much simpler when there is a fixed list of server agents with static ips. Otherwise, as @justinclayton mentioned, you'll have to use docker exec, which is buggy at the moment.

Anyway, thank you for all the great and inspiring work! =)

from docker-consul.

👍

from docker-consul.

+1

from docker-consul.

I would really like this as well, same usecase as above systemd script that takes many ipaddress (some might be dead) and tries to join all of them. a single --join= --join= would be easier than looping until ew find something to join.

from docker-consul.

👍

from docker-consul.

You can do multiple joins or whatever Consul arguments you like now.

from docker-consul.