lhotari opened a new issue, #25005: URL: https://github.com/apache/pulsar/issues/25005
### Search before reporting - [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](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment Issue was introduced in #14566, already in 2.10.5 ### Issue Description Before the #14566 change, the client would first subscribe to all topics and then send flow permits to the broker in the startReceivingMessages method. The behavioral change is that messages will start flowing from the broker to the client immediately. If subscribing to any of the partitions fails, it will add a lot of extra work to the system and could cause cascading failures when brokers are at their limits. It's better to fix this problem and remove the `newConsumer.resume();` lines added in this PR. ### Error messages ```text ``` ### Reproducing the issue TBD ### Additional information _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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
