From bb08378059df4a68de4d34af7b792a870489265c Mon Sep 17 00:00:00 2001 From: sdinakar85 Date: Fri, 7 Oct 2016 14:12:37 +0530 Subject: [PATCH] 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. --- website/source/docs/guides/datacenters.html.markdown | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/website/source/docs/guides/datacenters.html.markdown b/website/source/docs/guides/datacenters.html.markdown index e46c1ef8c2..f4ab956511 100644 --- a/website/source/docs/guides/datacenters.html.markdown +++ b/website/source/docs/guides/datacenters.html.markdown @@ -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 ... @@ -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,