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

update broken links

Browse Source 
add back nats.io link to outline
This commit is contained in:
ainsley
2019-06-04 15:55:57 -05:00
parent 386c157d0b
commit 13e2a3c7c4
6 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
nats_admin/slow_consumers.md
View File

@@ -1,6 +1,6 @@
## Slow Consumers
To support resiliency and high availability, NATS provides built-in mechanisms to automatically prune the registered listener interest graph that is used to keep track of subscribers, including slow consumers and lazy listeners. NATS automatically handles a slow consumer. If a client is not processing messages quick enough, the NATS server cuts it off. To support scaling, NATS provides for auto-pruning of client connections. If a subscriber does not respond to ping requests from the server within the [ping-pong interval](/nats-protocol/nats-protocol.md#PINGPONG), the client is cut off (disconnected). The client will need to have reconnect logic to reconnect with the server.
To support resiliency and high availability, NATS provides built-in mechanisms to automatically prune the registered listener interest graph that is used to keep track of subscribers, including slow consumers and lazy listeners. NATS automatically handles a slow consumer. If a client is not processing messages quick enough, the NATS server cuts it off. To support scaling, NATS provides for auto-pruning of client connections. If a subscriber does not respond to ping requests from the server within the [ping-pong interval](/nats-protocol.md#PINGPONG), the client is cut off (disconnected). The client will need to have reconnect logic to reconnect with the server.
# Slow Consumers