smbecker opened a new issue, #23941: URL: https://github.com/apache/pulsar/issues/23941
### Search before asking - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### Version 4.0 ### Minimal reproduce step * Create a `non-persistent` topic with a consumer and failover subscription * Notice that the consumer is never notified whether it is the active consumer or not I wrote a [minimal test](https://github.com/smbecker/pulsar-failover-subscriptions] demonstrating that `persistent` and `non-persistent` consumers are treated differently. ### What did you expect to see? I would expect consumer on `non-persistent` failover topics to be notified of active consumer changes similar to how they are notified in `persistent` topics. ### What did you see instead? Consumer on `non-persistent` failover topics are not notified of active consumer changes. ### Anything else? In looking at [PersistentDispatcherSingleActiveConsumer.java](https://github.com/apache/pulsar/blob/5e5d514174fdbc1b400df51fafaa18110f1c31a9/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentDispatcherSingleActiveConsumer.java#L115), you can see that there is a call to notify consumers of the change. However, in [NonPersistentDispatcherSingleActiveConsumer.java](https://github.com/apache/pulsar/blob/5e5d514174fdbc1b400df51fafaa18110f1c31a9/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/nonpersistent/NonPersistentDispatcherSingleActiveConsumer.java#L100), no attempt is made to notify consumers of the change. Is this by design? I would expect the behaviors to be consistent. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
