shibd opened a new issue, #15224:
URL: https://github.com/apache/pulsar/issues/15224
**Describe the bug**
In the current `MessageDeduplication` implementation, when the producer is
disconnected, the producer will be added to the inactiveProducers collection,
waiting to be expired and deleted.
But before the expired deletion, if the broker restarts and these producers
are no longer reconnected, then these producers will never be expired and
deleted
**To Reproduce**
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.
6. Restart broker.
**Expected behavior**
After waiting 2 minutes, all producers expired and delete.
**Actual behavior**
These producers will never be expired and deleted.
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
**Additional context**
Here is another question about the existence in MessageDeduplication, One of
the issues references #15204.
--
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]
