Open xuesongxs opened 2 years ago
Is it reproduced on master branch? Do you plan to work on a fix? @xuesongxs
Is it reproduced on master branch? Do you plan to work on a fix? @xuesongxs
I tested it on the 2.8.3 branch, the same should be true for the master branch, I won't fix this.
In this case, it may receive the duplicate message.
In this case, it may receive the duplicate message.
Because mark delete info is persistent periodically and it's not triggered when topic unloads?
In this case, it may receive the duplicate message.
Because mark delete info is persistent periodically and it's not triggered when topic unloads?
I unloaded or stopped the broker 5 minutes after the ack of the first 99 messages was completed. Even if I write index asynchronously, 5 minutes should be enough, but there is still a problem.
The issue had no activity for 30 days, mark with Stale label.
The issue had no activity for 30 days, mark with Stale label.
15031 and #15067 fix issues in this area.
I have verified these 2 PRs in the latest pulsar version and have not solved this bug.
The issue had no activity for 30 days, mark with Stale label.
2.8.4 duplicated delayed messages when unload topic
Describe the bug Pulsar v2.8.3 acknowledgmentAtBatchIndexLevelEnabled will still receive duplicate messages
To Reproduce Steps to reproduce the behavior:
Create consumer:
bin/pulsar-admin topics unload persistent://public/default/batchtest
Expected behavior Only push the message without ack.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.