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

GitBook: [master] 2 pages modified

Browse Source
This commit is contained in:
Ginger Collison 2021-06-30 13:31:10 +00:00 committed by gitbook-bot
parent e68a52fb00
commit 4e693c3a9a
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
2 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
jetstream/leafnodes.md
View File

@ -14,10 +14,6 @@ To disambiguate between servers, the option `domain` was added to the JetStream
There are reasons to connect system accounts on either end of your leaf node connection. You probably don't want to connect your cloud and edge device system accounts, but you might connect them when the only reason keeping you from using a super cluster are firewall rules. There are reasons to connect system accounts on either end of your leaf node connection. You probably don't want to connect your cloud and edge device system accounts, but you might connect them when the only reason keeping you from using a super cluster are firewall rules.
There are reasons to connect system accounts on either end of your leaf node connection. You probably don't want to connect your cloud and edge device system accounts, but you might connect them when the only reason keeping you from using a super cluster are firewall rules. The benefits are: 1\) monitoring of all connected nats-servers 2\) nats-account-resolver working on the entire network 3\) extended JetStream cluster
There are reasons to connect system accounts on either end of your leaf node connection. You probably don't want to connect your cloud and edge device system accounts, but you might connect them when the only reason keeping you from using a super cluster are firewall rules. The benefits are: 1\) monitoring of all connected nats-servers 2\) nats-account-resolver working on the entire network 3\) extended JetStream cluster
The benefits are: The benefits are:
* Monitoring of all connected nats-servers * Monitoring of all connected nats-servers

1
whats_new.md
View File

@ -7,6 +7,7 @@ The NATS.io team is always working to bring you features to improve your NATS ex
* [OCSP support](nats-server/configuration/ocsp.md) * [OCSP support](nats-server/configuration/ocsp.md)
### JetStream ### JetStream
* Richer API errors. JetStream errors now contain an ErrCode that uniquely describes the error. * Richer API errors. JetStream errors now contain an ErrCode that uniquely describes the error.
* Ability to send more advanced Stream purge requests that can purge all messages for a specific subject * Ability to send more advanced Stream purge requests that can purge all messages for a specific subject
* Stream can now be configured with a per-subject message limit * Stream can now be configured with a per-subject message limit