From 20046aa2ebdb332b9d7cf0bc9ac3a0b85d6e54c5 Mon Sep 17 00:00:00 2001 From: Bill Hass Date: Wed, 10 Feb 2021 16:34:11 -0500 Subject: [PATCH] Clarify Example Gateway Connection Logic The current description reads like each external gateway, B1 & B2, should have three connections from the local cluster because the local cluster has three gateway nodes. However, my understanding is that the external gateway _cluster_ will have three connections from the local cluster. Added cluster at the end of sentence and clarified there will be three outbound connections from the local cluster. --- nats-server/configuration/gateways/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-server/configuration/gateways/README.md b/nats-server/configuration/gateways/README.md index 89ce668..0bd811e 100644 --- a/nats-server/configuration/gateways/README.md +++ b/nats-server/configuration/gateways/README.md @@ -27,7 +27,7 @@ If gateways are to be used in a cluster, **all** servers of this cluster need to A nats-server in a gateway role will specify a port where it will accept gateway connections. If the configuration specifies other _external_ `gateways`, the gateway will create one outbound gateway connection for each gateway in its configuration. It will also gossip other gateways it knows or discovers. Fewer _external_ `gateways` mean less configuration. Yet, the ability to discover more gateways and gateway nodes depends on these servers running. This is similar to _seed server_ in cluster. It is recommended to have all _seed server_ of a cluster listed in the `gateways` section. -If the local cluster has three gateway nodes, this means there will be three outbound connections to each external gateway. +If the local cluster has three gateway nodes, this means there will be three outbound connections from the local cluster to each external gateway cluster. ![Gateway Connections](../../../.gitbook/assets/simple.svg)