luxolus/open-consul
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

Merge pull request #2397 from sdinakar85/patch-1

Browse source 
Multiple Datacenter Documentation
This commit is contained in:
James Phillips 2016-11-17 16:43:55 -08:00 committed by GitHub
parent 5a643c6e3f cafd59a45a
commit 916d0aa133
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 so they do not participate in WAN gossip. Client requests are forwarded by local
servers to a server in the target datacenter as necessary. 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 ```text
$ consul join -wan <server 1> <server 2> ... $ 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 $ 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 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, work. Of course, all server nodes must be able to talk to each other. Otherwise,