mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
dead links
This commit is contained in:
@@ -39,4 +39,4 @@ nats-server --signal stop=<pid>
|
||||
nats-server --signal stop=/path/to/pidfile
|
||||
```
|
||||
|
||||
See the [Windows Service](windows_srv.md) section for information on signaling the NATS server on Windows.
|
||||
See the [Windows Service](/nats_server/windows_srv.md) section for information on signaling the NATS server on Windows.
|
||||
@@ -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](/documentation/internals/nats-protocol/), 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/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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user