-
Notifications
You must be signed in to change notification settings - Fork 336
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
Ack/Nack use closed consumer #850
Comments
I will give an pr to fix this issue. |
billowqiu
added a commit
to billowqiu/pulsar-client-go
that referenced
this issue
Sep 21, 2022
2: add some log for pc
1 task
@billowqiu Do you want to contribute the fix back to apache/pulsar-client-go? |
I have submitted a pr in this link: #852 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
1:use Client to Subscribe a topic create an consumer-1
2:Receive message use consumer-1
3:then in some case consumer-1 is Closed.
4:use the same Client to create another consumer-2 to Ack/Nack the message
expect consumer-2 to Ack/Nack the message
Actual behavior
the Ack/Nack will use consumer-1 which is Closed before.
Tell us what happens instead
Steps to reproduce
1:use Client to Subscribe a topic create an consumer-1
2:Receive message use consumer-1
3:then in some case consumer-1 is Closed.
4:use the same Client to create another consumer-2 to Ack/Nack the message
System configuration
Pulsar version: x.y
The text was updated successfully, but these errors were encountered: