getRedeliveryCount always return 0

Open
#296 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, nodejs
Domain
distributed-systems

Research direction

Start with the message.getRedeliveryCount() and subscribe entry points, then reproduce the behavior using pulsar-client v1.8 against Pulsar 2.10.0 while acknowledging with nack and keeping the client connected. Done means the redelivery count reflects repeated deliveries, or the issue documents the supported behavior and cause of the constant zero.

Written by the indexing model from the issue text.

Description

Hello,

Is there a way to make message.getRedeliveryCount() return the number of time a message has been redelivered?
I hope it's not a problem between the chair and the keyboard, but in my case, the function always returns 0.

I tried to let the default parameters on subscribe, but it doesn't change anything.
There is no disconnection of the client between each redelivery.
The message is well nack each time.

i use pulsar-client v1.8 and kezhenxu94/pulsar pulsar container (pulsar 2.10.0).

Dominant language
C++
Stars
164
Forks
99
Avg merge
5d 18h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/pulsar-client-node

All issues in apache/pulsar-client-node

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.