rvashishth opened a new issue #11445: URL: https://github.com/apache/pulsar/issues/11445
**Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Create pulsar cluster with version 2.7.1 2. enabled topic level policy at broker config. https://pulsar.apache.org/docs/en/pulsar-admin/#topics-1 3. created a topic and set the deduplicationEnabled to true 4. Created a pulsar producer with a static name and set the timeout to 0 second https://pulsar.apache.org/docs/en/cookbooks-deduplication/ 5. produce message with same sequenceId and consume 6. But still I am able to produce and consume multiple message with same sequence id. **Expected behavior** Broker must not persist two message with same service id **Screenshots** NA **Desktop (please complete the following information):** Deployed pulsar on AKS **Additional context** How can we handle producer timeout if producer always must have the timeout set to 0(means effective no timeout) -- 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]
