bardock opened a new issue #2431: Unable to consume messages, need to re-subscribe client URL: https://github.com/apache/incubator-pulsar/issues/2431 This is similar to issue [2013](https://github.com/apache/incubator-pulsar/issues/2013). We have several shared subscriptions of partitioned topics and we found some cases where a subscription's client is not receiving messages, but it's not related to a specific topic partition. In this case, if we re-subscribe the client (`PulsarClient.subscribeAsync`), messages start to be delivered as expected. Client logs this warn: ``` [log_time:16:17:42.377] [thread:pulsar-timer-6-1] [level:WARN ] [logger:UnAckedMessageTracker] - [ConsumerBase{subscription='picking-consumer-prod.fbm-wms-picking', consumerName='i-08e97d991d75e9d07-10.73.125.156', topic='persistent://fury/global/wms-wave-feed-prod.fbm-wms-picking/wms-wave-feed-prod.fbm-wms-picking'}] 1 messages have timed-out ``` And we don't see any error from brokers. Any idea? Any log or metric that may be useful to debug this problem? #### System configuration **Pulsar version (brokers)**: 1.20.0 **Pulsar clients version**: 1.22.0 **Bookkeeper version**: 4.7.1
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
