addisonj commented on issue #14082:
URL: https://github.com/apache/pulsar/issues/14082#issuecomment-1032045634
@anant-ahuja
1. From the topic stats, at the subscription level, you can see
```
"msgBacklog" : 24,
"backlogSize" : 0,
"msgBacklogNoDelayed" : 24,
"blockedSubscriptionOnUnackedMsgs" : false,
"msgDelayed" : 0,
"unackedMessages" : 24,
```
Note that msgBacklog and unackedMessages are both the same value. This means
that all the remaining 24 messages have been dispatched to the consumer (i.e.
they are waiting in the receive queue), but have not been processed/acked by
the application. In other words, msgBacklog still counts messages that have
been dispatched but not yet acknowledged.
Both your examples show the same effect.
So I think your confusion is simply on the definition of msgBacklog, they
have been sent, they just have not been acked.
Just to answer your other questions though
2. There are two situations in which you might see the broker stop
delivering messages
a) there are no available permits in any of your consumers
b) the unacked messages goes about the configured max outstanding value
(which is something like 50k)
3. If case B above is true, then yes, that field should be set to true.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
