lhotari opened a new issue, #23845: URL: https://github.com/apache/pulsar/issues/23845
### Search before asking - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### Version Pulsar 4.0.1 ### Minimal reproduce step Exact steps to reproduce aren't yet confirmed. This problem was faced in a test where there was a large number of consumers that were scaled in a way where consumers were added and removed. The problem was noticed at the end of the test case, where all messages didn't get delivered to consumers and remained in the backlog. In the topic stats for the subscription, `msgInReplay` showed a positive value and in internal stats for the subscription `subscriptionHavePendingRead` was true. By looking at the code, it seems to be a case that isn't handled for PersistentDispatcherMultipleConsumers/PersistentStickyKeyDispatcherMultipleConsumers. ### What did you expect to see? The cursor shouldn't go into completely into "waiting" state when there are messages in the replay queue. ### What did you see instead? Messages in the replay queue don't get dispatched to consumers. ### Anything else? _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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: commits-unsubscr...@pulsar.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org