srouthu1 opened a new issue #9288: URL: https://github.com/apache/pulsar/issues/9288
#### Expected behavior we have 6 bookies, with Ensemble=3, Qw=2, Qa=2. While the consumer consuming the messages, Two bookies were brought down which are part of Qw. Broker should dispatch the messages to consumer which are available in the New Ensemble. If the bookies are up after some time, then the broker should dispatch the messages from these bookies as consumer can't afford message loss. #### Actual behavior Publisher is able to continue as the ensemble is formed with other available bookies. But consumer got stuck indefinitely waiting for the messages in the bookies which are down. We have autoSkipNonRecoverableData=true which did not help. We have restarted the owner broker also but it did not help. The consumer resumed when we brought back the bookies which are holding messages. The consumer also resumed when we run reset-cursor command but this is not a feasible solution with thousands of topics #### Steps to reproduce Ensemble=3, Qw=2, Qa=2. Total bookies=5 or 6. Continuously Publish and consume to a topic. Ensure consumer is slower than publisher. Bring down 2 bookies at the same time. Verify if consumer is able to resume the consumption. #### System configuration Pulsar version: 2.6 We are running on AWS. ---------------------------------------------------------------- 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]
