shibd opened a new issue, #15204:
URL: https://github.com/apache/pulsar/issues/15204
**Describe the bug**
In the implementation of `MessageDeduplication`, when producer is closed and
waits until it inactive, `HighestSequence` does not properly remove these
producers.
**To Reproduce**
Steps to reproduce the behavior:
1. Change messageDeduplication config on `standalone.conf`:
```
brokerDeduplicationEnabled=true
brokerDeduplicationMaxNumberOfProducers=10000
brokerDeduplicationSnapshotFrequencyInSeconds=10
brokerDeduplicationSnapshotIntervalSeconds=60
brokerDeduplicationEntriesInterval=10
brokerDeduplicationProducerInactivityTimeoutMinutes=2
```
3. Start pulsar standalone.
4. Create some produces and send messages.
5. Close or stop these producers.
**Expected behavior**
After waiting 2 minutes, execute the following command, and these producer
information are deleted from cursor#pulsar.dedup`
```
pulsar-admin topics stats-internal test-topic
```
**Screenshots**
These production information will never be deleted.
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- master branch
**Additional context**
Add any other context about the problem here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
