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
[pulsar-client] Fix pending queue-size stats for batch messages #12704
Conversation
@rdhabalia:Thanks for your contribution. For this PR, do we need to update docs? |
1 similar comment
@rdhabalia:Thanks for your contribution. For this PR, do we need to update docs? |
389e722
to
8ba55d8
Compare
@rdhabalia seems that this is a bug fix and does not affect the user guide, so no need to update docs here? |
@Anonymitaet it won't require doc change. |
@rdhabalia thanks. when submitting a PR, can you help provide a doc label (tick the box)? Thanks |
(cherry picked from commit 9a3e7ec)
Motivation
Right now, pulsar-client prints stats with incorrect pending queue size for the batch messages. if the user configures batch-message size 100 (or batch delay is 10ms) and publishes 1000 messages then the producer prints stats with < 10 pending messages instead 1000 messages which is published by user. It confuses the user because the user sees a different counter than actual published messages. it creates confusion when the user gets ProducerQueueFull Error and stats prints queue size is 10 and allowed pending-messages are 1000.
Modification
Show correct pending messages for batch messages.