Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Non-persistent failover topics are not notified on active consumer changes #23941

Open
3 tasks done
smbecker opened this issue Feb 6, 2025 · 0 comments
Open
3 tasks done
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@smbecker
Copy link

smbecker commented Feb 6, 2025

Search before asking

  • I searched in the issues and found nothing similar.

Read release policy

  • 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 demonstrating that persistent and non-persistent consumers are treated differently.

What did you expect to see?

I would expect consumers 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?

Consumers on non-persistent failover topics are not notified of active consumer changes.

Anything else?

In looking at PersistentDispatcherSingleActiveConsumer.java, you can see that there is a call to notify consumers of the change. However, in NonPersistentDispatcherSingleActiveConsumer.java, 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?

  • I'm willing to submit a PR!
@smbecker smbecker added the type/bug The PR fixed a bug or issue reported a bug label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

No branches or pull requests

1 participant