e-marchand-exensa commented on issue #8307: URL: https://github.com/apache/pulsar/issues/8307#issuecomment-839851849
> 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 . I'm not 100% sure the messages get delivered, but the backlog goes empty after restart, as far as I could see. Still, the future should have completed. > 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. I do have a thread dump before stopping the application. [wdl_prod_22_thread_dump.log](https://github.com/apache/pulsar/files/6467048/wdl_prod_22_thread_dump.log) > Are you using an ordinary consumer subscribing to a single topic or is it a multi-topic consumer? It is a single topic consumer. Here is the extract for the `consumer` creation. ``` final var builder = pulsarClient.newConsumer() .consumerName( consumerName ) .topic( topic ) .subscriptionName( subscription ) .subscriptionType( SubscriptionType.Exclusive ) .subscriptionInitialPosition( SubscriptionInitialPosition.Latest ) .batchReceivePolicy( batchPolicy ) .receiverQueueSize( batchPolicy.getMaxNumMessages() > 0 ? 2*batchPolicy.getMaxNumMessages() : 1024 ) .maxTotalReceiverQueueSizeAcrossPartitions( 32 * 1024 ) .acknowledgmentGroupTime( 250, TimeUnit.MILLISECONDS ); ``` with the following `batchPolicy` ``` BatchReceivePolicy.builder() .maxNumMessages( 42 ) .maxNumBytes( -1 ) // FIXME: because of issue #7696 in Pulsar v2.5.2 .timeout( 1, TimeUnit.SECONDS ); ``` For this topic, `maxNumMessages` is 1024 and `timeout` is 1000ms. -- 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]
