taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

incorporating suggestions

Browse Source 
Signed-off-by: Matthias Hanel <mh@synadia.com>
This commit is contained in:
Matthias Hanel 2021-06-28 20:10:31 -04:00
parent ebc257e36f
commit 62a46ca305
No known key found for this signature in database
GPG Key ID: 15514DE17E348F7E
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
jetstream/leafnodes.md
View File

@ -9,7 +9,7 @@ The general issue with multiple, independent JetStreams, accessible from the sam
As an example, consider a leafnode with a non-clustered JetStream in each server.
You connect to one of them, but which JetStream responds when you use the JetStream API `$JS.API.>` ?
To disambiguate that, the option `domain` was added to the JetStream configuration block.
To disambiguate between servers, the option `domain` was added to the JetStream configuration block.
When using it, follow these rules:
Every server in a cluster and super cluster needs to have the same domain name.
This means that domain names can only change between two servers if they are connected via a leafnode connection.
@ -377,7 +377,7 @@ All of the above happened in the same account.
To share domain access across accounts the `account.conf` from above needs to be modified and the server restarted or reloaded.
This example exports the consumer API as well as a delivery subject which is used by the internal push consumer created by `source` and `mirror`.
In support of an example on how to share a durable consumer for client access across domains and accounts, the `NEXT` and `ACK` API are exported as well.
In support of another example on how to share a durable consumer for client access across domains and accounts, the `NEXT` and `ACK` API are exported as well.
On import, the JetStream API prefix `$JS.hub.API` is renamed to `JS.test@hub.API`.
This is to, once more, disambiguate which JetStream a client in the importing account might want to interact with.