-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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] Unacked message counter is wrong #21568
Labels
type/bug
The PR fixed a bug or issue reported a bug
Comments
15 tasks
poorbarcode
pushed a commit
that referenced
this issue
Nov 30, 2023
…n on non-persistent topic (#21592) Fixes #21568 Motivation Fix incorrect unack count when using shared subscription on non-persistent topic Modifications In the case of a non-persistent topic, the consumer does not send an ack to the broker (see org.apache.pulsar.client.impl.NonPersistentAcknowledgmentGroupingTracker# addAcknowledgment) To work around this, we can update unackedMessages when the broker sends a message to the consumer successfully.
Technoboy-
pushed a commit
that referenced
this issue
Dec 3, 2023
…n on non-persistent topic (#21592) Fixes #21568 Motivation Fix incorrect unack count when using shared subscription on non-persistent topic Modifications In the case of a non-persistent topic, the consumer does not send an ack to the broker (see org.apache.pulsar.client.impl.NonPersistentAcknowledgmentGroupingTracker# addAcknowledgment) To work around this, we can update unackedMessages when the broker sends a message to the consumer successfully.
Technoboy-
pushed a commit
that referenced
this issue
Dec 4, 2023
…n on non-persistent topic (#21592) Fixes #21568 Motivation Fix incorrect unack count when using shared subscription on non-persistent topic Modifications In the case of a non-persistent topic, the consumer does not send an ack to the broker (see org.apache.pulsar.client.impl.NonPersistentAcknowledgmentGroupingTracker# addAcknowledgment) To work around this, we can update unackedMessages when the broker sends a message to the consumer successfully.
Technoboy-
pushed a commit
that referenced
this issue
Dec 4, 2023
…n on non-persistent topic (#21592) Fixes #21568 Motivation Fix incorrect unack count when using shared subscription on non-persistent topic Modifications In the case of a non-persistent topic, the consumer does not send an ack to the broker (see org.apache.pulsar.client.impl.NonPersistentAcknowledgmentGroupingTracker# addAcknowledgment) To work around this, we can update unackedMessages when the broker sends a message to the consumer successfully.
nikhil-ctds
pushed a commit
to datastax/pulsar
that referenced
this issue
Dec 20, 2023
…n on non-persistent topic (apache#21592) Fixes apache#21568 Motivation Fix incorrect unack count when using shared subscription on non-persistent topic Modifications In the case of a non-persistent topic, the consumer does not send an ack to the broker (see org.apache.pulsar.client.impl.NonPersistentAcknowledgmentGroupingTracker# addAcknowledgment) To work around this, we can update unackedMessages when the broker sends a message to the consumer successfully.
srinath-ctds
pushed a commit
to datastax/pulsar
that referenced
this issue
Dec 20, 2023
…n on non-persistent topic (apache#21592) Fixes apache#21568 Motivation Fix incorrect unack count when using shared subscription on non-persistent topic Modifications In the case of a non-persistent topic, the consumer does not send an ack to the broker (see org.apache.pulsar.client.impl.NonPersistentAcknowledgmentGroupingTracker# addAcknowledgment) To work around this, we can update unackedMessages when the broker sends a message to the consumer successfully.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
Version
Both 2.11.2 and 3.1.1 images
Minimal reproduce step
Code example:
What did you expect to see?
When I run
I expected to see unackedMessages equal to zero
What did you see instead?
Instead, I'm seeing unackedMessages not equal to zero but it's growing with every processed message
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: