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

fixed leaf node spelling

Browse Source
This commit is contained in:
Ginger Collison 2021-06-29 11:34:00 -05:00 committed by GitHub
parent 85b10a920f
commit 1b41359b31
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
jetstream/leafnodes.md
View File

@ -2,7 +2,7 @@
If you want to see a demonstration of the full range of this functionality, check out our [video](https://youtu.be/0MkS_S7lyHk) If you want to see a demonstration of the full range of this functionality, check out our [video](https://youtu.be/0MkS_S7lyHk)
One of the use cases for leafnodes is to provide a local NATS network even when the connection to a hub or the cloud is down. One of the use cases for a NATS server configured as a [leaf node](/nats-server/configuration/leafnodes) is to provide a local NATS network even when the connection to a hub or the cloud is down.
To support such a disconnected use case with JetStream, independent JetStream islands are also supported and available through the same NATS network. To support such a disconnected use case with JetStream, independent JetStream islands are also supported and available through the same NATS network.
The general issue with multiple, independent JetStreams, accessible from the same client is that you need to be able to tell them apart. The general issue with multiple, independent JetStreams, accessible from the same client is that you need to be able to tell them apart.
@ -24,7 +24,7 @@ The benefits are:
3) extended JetStream cluster 3) extended JetStream cluster
When `domain` is set, JetStream-related traffic on the system account is suppressed. When `domain` is set, JetStream-related traffic on the system account is suppressed.
This is what causes JetStream to not be extended. This is what causes JetStream not to be extended.
In addition, traffic on `$JS.API.>` is also suppressed. In addition, traffic on `$JS.API.>` is also suppressed.
This causes clients to use the local JetStream that is available in the nats-servers they are connected to. This causes clients to use the local JetStream that is available in the nats-servers they are connected to.