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

Multiple Datacenter Documentation 

Updated the slightly confusing documentation on how to join the clusters over WAN. Also the inputs from #1656 is taken in account in this documentation update.
This commit is contained in:
sdinakar85 2016-10-07 14:12:37 +05:30 committed by GitHub
parent eb44c4cf5d
commit bb08378059
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/guides/datacenters.html.markdown
View File

@ -33,7 +33,7 @@ only contain server nodes. Client nodes send requests to a datacenter-local serv
so they do not participate in WAN gossip. Client requests are forwarded by local
servers to a server in the target datacenter as necessary.
The next step is to ensure that all the server nodes join the WAN gossip pool:
The next step is to ensure that all the server nodes join the WAN gossip pool (include all the servers in all the datacenters):
```text
$ consul join -wan <server 1> <server 2> ...
@ -65,6 +65,16 @@ $ curl http://localhost:8500/v1/catalog/nodes?dc=dc1
$ curl http://localhost:8500/v1/catalog/nodes?dc=dc2
...
```
In order to persist the `join` information, the following can be added to the `consul` configuration in each of the `server` nodes in the cluster. For example, in `dc1` server nodes:
```
...
"retry_join_wan":[
"dc2-server-1",
...
"dc2-server-N",
],
...
```
There are a few networking requirements that must be satisfied for this to
work. Of course, all server nodes must be able to talk to each other. Otherwise,