From 2dcb7fc68795c6d3f8f484d7c48d72176916a25e Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 30 May 2019 12:52:58 -0500 Subject: [PATCH] Update slow_consumers.md --- nats_admin/slow_consumers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/nats_admin/slow_consumers.md b/nats_admin/slow_consumers.md index 096a9e3..8eda47d 100644 --- a/nats_admin/slow_consumers.md +++ b/nats_admin/slow_consumers.md @@ -64,11 +64,11 @@ The server will also keep count of the number of slow consumer errors encountere ## Handling slow consumers -Apart from using [NATS streaming](nats_streaming/intro.md/) or optimizing your consuming application, there are a few options available: scale, meter, or tune NATS to your environment. +Apart from using [NATS streaming](/nats_streaming/intro.md/) or optimizing your consuming application, there are a few options available: scale, meter, or tune NATS to your environment. __Scaling with queue subscribers__ -This is ideal if you do not rely on message order. Ensure your NATS subscription belongs to a [queue group](http://nats.io/documentation/concepts/nats-queueing/), then scale as required by creating more instances of your service or application. This is a great approach for microservices - each instance of your microservice will receive a portion of the messages to process, and simply add more instances of your service to scale. No code changes, configuration changes, or downtime whatsoever. +This is ideal if you do not rely on message order. Ensure your NATS subscription belongs to a [queue group](/developer/concepts/queue.md/), then scale as required by creating more instances of your service or application. This is a great approach for microservices - each instance of your microservice will receive a portion of the messages to process, and simply add more instances of your service to scale. No code changes, configuration changes, or downtime whatsoever. __Create a subject namespace that can scale__ @@ -110,4 +110,4 @@ if err := sub.SetPendingLimits(1024*500, 1024*5000); err != nil { The default subscriber pending message limit is `65536`, and the default subscriber pending byte limit is `65536*1024` -If the client reaches this internal limit, it will drop messages and continue to process new messages. This is aligned with NATS at most once delivery. It is up to your application to detect the missing messages and recover from this condition. \ No newline at end of file +If the client reaches this internal limit, it will drop messages and continue to process new messages. This is aligned with NATS at most once delivery. It is up to your application to detect the missing messages and recover from this condition.