lhotari commented on issue #8307: URL: https://github.com/apache/pulsar/issues/8307#issuecomment-839744437
> Since this issue, I'm still using `pulsarConsumer.batchReceiveAsync().get( 10, TimeUnit.SECONDS )` in my client code to be sure not to block even if the `BatchReceivePolicy` is configured with a timeout of 1s using Pulsar v2.6.2. > > I just encountered the issue again, the future not completing after 10s and the consumer never receiving anything anymore while the backlog is growing. **This time, I can't see any log from Pulsar (client side)**. All off the many others consumers are still working properly. It seems a random thing, so I guess a race condition somewhere. > > I don't see anything in Pulsar v2.6.3 or v2.7.1 that could solve this issue, do you have any insight to share ? > > Regards. @e-marchand-exensa It's possible that you are encountering a different issue since there are no log messages. Do the messages get delivered when you restart the client side? If not, then it must be a problem on the broker side. For example, some fixes have been recently made to a condition where the message delivery stops, an issue reported as #6054 . Would you be able to create a thread dump of the Java process where this occurs? When using the Pulsar docker images, a thread dump can be created by running `jstack 1` in the shell. Are you using an ordinary consumer subscribing to a single topic or is it a multi-topic consumer? -- 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. For queries about this service, please contact Infrastructure at: [email protected]
