status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Put back manual process steps

This commit is contained in:
Brian Shumate 2017-04-13 15:20:02 -04:00
parent 626d5264a8
commit d0fdc39bf9
No known key found for this signature in database
GPG Key ID: B2E211633F870928
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
website/source/docs/guides/bootstrapping.html.markdown
View File

@ -55,6 +55,25 @@ Choose the method which best suits your environment and specific use case.
~> **Notice:** The hosted version of Consul Enterprise was deprecated on ~> **Notice:** The hosted version of Consul Enterprise was deprecated on
March 7th, 2017 and the Atlas `auto-join` feature is no longer available. For details, see https://atlas.hashicorp.com/help/consul/alternatives. March 7th, 2017 and the Atlas `auto-join` feature is no longer available. For details, see https://atlas.hashicorp.com/help/consul/alternatives.
### Manually Creating a Cluster
To manually create a cluster, access one of the machines and run the following:
```
$ consul join <Node A Address> <Node B Address> <Node C Address>
Successfully joined cluster by contacting 3 nodes.
```
Since a join operation is symmetric, it does not matter which node initiates it. Once the join is successful, one of the nodes will output something like:
```
[INFO] consul: adding server foo (Addr: 127.0.0.2:8300) (DC: dc1)
[INFO] consul: adding server bar (Addr: 127.0.0.1:8300) (DC: dc1)
[INFO] consul: Attempting bootstrap with nodes: [127.0.0.3:8300 127.0.0.2:8300 127.0.0.1:8300]
...
[INFO] consul: cluster leadership acquired
```
## Verifying the Cluster ## Verifying the Cluster
As a sanity check, the [`consul info`](/docs/commands/info.html) command As a sanity check, the [`consul info`](/docs/commands/info.html) command