Implementing bootstrap-expect

[kshep]

Per the current Consul docs:

The recommended way to bootstrap is to use the -bootstrap-expect configuration option. This options informs Consul of the expected number of server nodes, and automatically bootstraps when that many servers are available. To prevent inconsistencies and split-brain situations, all servers should specify the same value for -bootstrap-expect or specify no value at all. Any server that does not specify a value will not attempt to bootstrap the cluster.

-- http://www.consul.io/docs/guides/bootstrapping.html

Should there be a new ['consul']['service_mode'] setting for bootstrap-expect?

I'd be happy to tackle this and submit a PR if it's not a high priority for anybody else.

[johnbellone]

@pyanni and I were talking about this yesterday. I am going to defer to him for some insight. But if you have a few free cycles and want to jam out a PR we'd definitely accept it.

[lawsonj2019]

Is this not as simple as modifying the _service.rb recipe in the case statement so that clusters can also have a start_join list? All the hard work has already been done, it's just a case of adding service_config['start_join'] = node['consul']['servers'] when you have a cluster with a known bootstrap_expect value.

when 'cluster'
  service_config['server'] = true
  if num_cluster > 1
    service_config['bootstrap_expect'] = num_cluster
    service_config['start_join'] = node['consul']['servers']
  else
    service_config['bootstrap'] = true
  end

Or does this have unintended side effects I'm not aware of?

I've tested this with a three-node vagrant cluster and it auto bootstraps the cluster and elects a leader.

[johnbellone]

I am going to have to test that a bit. Would you mind submitting a PR and referencing this issue?

[kainosnoema]

This looks resolved to me. Thanks!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.