apache / apache/pulsar-client-node
Consumer.acknowledge() not registered in client
- Dominant language
- C++
- Stars
- 164
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
After receiving a message, our script makes an API call through axios to process the pulsar message. consumer.receive() and the processing logic runs in a while loop until receive() times out when the queue is empty.
It appears if we run acknowledge() prior to the API call, the client behaves correctly, that is messages are acked and receive does not receive any more messages once all messages are acked.
But running ack after the API call, the desired way to ack the message, it seems as receive() goes in a loop and keeps receiving messages already acked. However if we quit the script and re-run it, the queue is indeed empty and no messages are received, similarly peaking the messages through pulsar-admin for the given topic-partition while the script is running confirm messages are acked.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the while loop using consumer.receive() and acknowledge() around the axios processing call, comparing acknowledgement before and after the API request. Check whether receive() returns already acknowledged messages until its timeout, and use pulsar-admin to compare the topic-partition state while the client runs. Done means acknowledgements after processing prevent further delivery of those messages without requiring a client restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100