Lanayx opened a new issue #4849: Acknowledged messages get redelivered after broker failure URL: https://github.com/apache/pulsar/issues/4849 **Describe the bug** I'm expecting redelivery of the old acknowleged messages after one broker failure on default minikube helm installation. **To Reproduce** I'm testing basic pub/sub pulsar functionality in minikube. There is topic "public/default/test" with default settings. I'm using the same exclusive subscription "test-subscription" all them time. I register producer which produces 100 messages and consumer which consumes them and acks all messages one by one as they arrive, they run concurrently. I can run this many times and it works ok all the times. Then I want to test broker failure, I have 2 of them in local cluster and 1 proxy. Steps to reproduce the behavior: 1. Run test before shutting down broker - everything works correctly, all messages produced and acknowledged 2. Shutdown one of brokers 3. Run the test again 4. After some reconnects are done internally - I get some random number of last messages from step1 **Expected behavior** I expect that after messages are acknowledged successfully they never get into the same subscription again. **Screenshots** Here is a screenshot of messages from the 1st step that were received on 4th step  **Desktop (please complete the following information):** - OS: Windows - Environment: minikube **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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
