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:
parent
03027260dc
commit
f0cc4ae8a3
|
@ -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,
|
||||||
|
|
Loading…
Reference in New Issue