[GitHub] [pulsar] sijie commented on issue #4137: Incorrect behavior single Pulsar Client creating multiple consumers

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

sijie commented on issue #4137: Incorrect behavior single Pulsar Client creating multiple consumers
URL: https://github.com/apache/pulsar/issues/4137#issuecomment-486880030
 
 
   I think #3743 was attempting to revert to the change and #3746 comes up a fix with reference counting. If reverting, we need to revert all related changes. So I would suggest holding a bit on reverting. Let’s discuss it to see if there is any other fixes. If there is no, I am fine with reverting all the changes.
   
   For the issue that functions is facing, I think it comes from MessageListener. Because if consumers are using receive and receiveAsync, the messages should be spreading across the instances calling the methods of a same consumer. So the fix for this issue can be:
   
   1) add the support for multiple message listeners.
   
   Or 
   
   2) set the consumer name in functions.
   
   Regarding the semantic question Matteo raises, I don’t know how to address his concern.
   
   Regarding the unack redeliver behavior, the unacked messages will still be redeliverd to consumer-2 when ack time-out happens.

----------------------------------------------------------------
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


With regards,
Apache Git Services