[Bug] msgbacklog grows infinitely after sending a certain amount of messages

[g0715158]

Search before asking

• I searched in the issues and found nothing similar.

Read release policy

• I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

3.0.1

Minimal reproduce step

1. Send 1000 messages and stop the producer process
2. msgbacklog has 1000 messages
3. Consume 1,000 messages and stop the consumer process
4. After the consumer stops, msgbacklog is 0

What did you expect to see?

msgbacklog sees messages that are equal to or less than the number of messages I sent

What did you see instead?

The producer stops sending after sending a batch of messages. When subscribing to these states, it is found that the msgbacklog value has been growing continuously.

Anything else?

This problem occurs when I set replicateSubscriptionState to true in the consumer！！！

After both the producer and the consumer are stopped, the msgbacklog has been growing slowly, and no additional messages will be consumed when the consumer is restarted.

Are you willing to submit a PR?

• I'm willing to submit a PR!

[lhotari]

@g0715158 please share exact steps with commands to reproduce this issue. The goal of the reproducing steps is that someone else could follow the instructions and reproduce the issue. The current description of reproducing steps isn't helpful at the moment.

[lhotari]

3.0.1

Does this problem also reproduce with the 3.0.7 version of Pulsar broker and Pulsar client? How about 4.0.0 ?