dao-jun commented on issue #21104: URL: https://github.com/apache/pulsar/issues/21104#issuecomment-2140860378
> I've noticed that with Client 3.2.2 the behavior may be a bit different. The consumers get blocked, but occasionally resume. After a couple messages received are stuck again. Stats are uploaded: https://github.com/michalcukierman/pulsar-21104/tree/main/stats > > I've confirmed once again, the issue does not occur with Pulsar Client 3.0.4 (or at least I was not able to reproduce it after processing 1 mln messages. With Client 3.2.2 usually clients are blocked after 50k messages). I check the [stats](https://github.com/michalcukierman/pulsar-21104/blob/main/stats/stats-0) and the [internal-stats](https://github.com/michalcukierman/pulsar-21104/blob/main/stats/stats-internal-0), As I can see, there is about 30k messages in the topic, and there is a subscription named `request-shared-subscription` to consume the topic, but it seems none of the messages acknowledged, the `markDeletedPosition` is `0:-1` and `individuallyDeletedMessages` is empty:  Which means all the messages are unacked, or, in the backlog. And I checked the `stats`, for the consumer of `request-shared-subscription`. I can see `msgOutCounter=10002` which means how many messages dispatched to the consumer, `unackedMessages=10001` means 10001 messages are unacked. So, obviously, you only receive messages but didn't ack messages. I guess the configuration `maxUnackedMessagesPerConsumer` in your `broker.conf` is `10000`. So, since the `unackedMessages=10001` exceeds the `maxUnackedMessagesPerConsumer=10000`, so the `blockedConsumerOnUnackedMsgs` field in the `stats` is true.  Which means there are toooo many unacked messages on the consumer so that the consumer stopped dispatch messages to clients. Please ack message after process successfully. -- 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]
