Open sijie opened 3 years ago
Any work around for this? We are facing same issue in AWS , production setup?
Facing this issue in following scenario:
We have 4 bookies. We are using (4,3,1) persistency. Stopped one of the bookie. We are seeing that recovery process is keep throwing the above error
Original Issue: apache/pulsar#9007
pulsar broker version 2.7.0 bookkeeper version 4.10.0
Pulsar Broker Error log when client producer message