[GitHub] [pulsar] alexku7 commented on issue #8115: Some partitions get stuck after adding additional consumers to the KEY_SHARED subscriptions

[GitBox <gi...@apache.org>]

alexku7 commented on issue #8115:
URL: https://github.com/apache/pulsar/issues/8115#issuecomment-701382177


   Hello
   The last status of this issue:
   
   1. It happens in most cases when we add new consumers and remove old or sometime when any current consumer is disconnected and reconnected becasue of small network interruptions.
   
   2. We see some unacked messages (1-5 messages. not more) on the subscription level but zero number of unacked messages on every consumer with 1000 available permits
   
   
   My guess is that these unacked messages belong to the old consumers that already disconnected and went away forever.
   
   We tried to sen ackTimout flag without success
   We tried to set setAllowOutOfOrderDelivery=true to set the relaxed ordering policy still without success
   We tried to send ack on every message but still can't avoid this issue
   
   
   Seems that the broker simply stopped dispatching messages and wait for something forever.
   
   In order to recover from this situation and resume  the dispatching we need to perform the one of the following :
   1. to unload the topic or
   2. to disconnected the all connected consumer (all of them!) and reconnect again.
   
   
   Some very strange bug. Seems we need to make the broker to be able to resume dispatching after some timeout despite the fact it has some unacked messages.
   
   Any suggestions ?
   
   


----------------------------------------------------------------
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:
users@infra.apache.org