mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
Including an example of ack wait
Signed-off-by: Matthias Hanel <mh@synadia.com>
This commit is contained in:
parent
ded758e784
commit
319370bc25
@ -16,6 +16,15 @@ sub, err := sc.Subscribe("foo",
|
|||||||
}, stan.SetManualAckMode(), stan.AckWait(aw))
|
}, stan.SetManualAckMode(), stan.AckWait(aw))
|
||||||
```
|
```
|
||||||
|
|
||||||
|
> Note that if processing a particular message exceeds ack wait, the following behavior can be observed with [queue subscriptions](queues.md):
|
||||||
|
> 1. Subscriber A receives the message.
|
||||||
|
> 2. Subscriber A exceeds ack wait time and Subscriber B receives the message.
|
||||||
|
> 3. Subscriber B exceeds ack wait time and Subscriber C receives the message.
|
||||||
|
> 6. Subscriber A finishes processing and acknowledges the message.
|
||||||
|
> 7. Re-delivery of the message ceases.
|
||||||
|
>
|
||||||
|
> How often the message is re-delivered depends on processing time for the message and available subscriber.
|
||||||
|
|
||||||
## Max In Flight
|
## Max In Flight
|
||||||
|
|
||||||
Subscribers can set max in flight to rate limit incoming messages. The server will send at most “max in flight” messages before receiving an acknowledgement. Setting max in flight to 1 insures every message is processed in order.
|
Subscribers can set max in flight to rate limit incoming messages. The server will send at most “max in flight” messages before receiving an acknowledgement. Setting max in flight to 1 insures every message is processed in order.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user