blankensteiner commented on issue #250:
URL: 
https://github.com/apache/pulsar-dotpulsar/issues/250#issuecomment-2636262435

   Hi @smbecker 
   
   As @entvex wrote, we need all the information to be able to help effectively.
   
   I have tested failover subscriptions on persistent and non-persistent topics 
on broker versions 2.11.4, 3.0.9, 3.1.2, 3.3.4, 4.0.0, and 4.0.2. I think there 
is a broker issue here.
   DotPulsar expects that the broker will tell the consumer if it is active or 
inactive. 
   This happens correctly on all versions for persistent topics.
   For non-persistent topics, it seems that if the first consumer is active and 
the second consumer is inactive, none of them are told what they are.  However, 
messages are sent to the first consumer.
   If the first consumer is made inactive by the second consumer, the first 
consumer is told that it is now inactive but the second isn't told that it is 
active. 
   If the active consumer is disposed, the other consumer isn't informed that 
it is now the active one.
   So, the "active" message is never sent and the "inactive" message is never 
sent initially, it is only sent if the consumer was active and is made inactive.
   
   It would make sense for the broker to have the same active/inactive 
messaging logic no matter if the topics are persistent or non-persistent.


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to