sijie commented on issue #6603: Brokers fail when updating bookkeeper URL: https://github.com/apache/pulsar/issues/6603#issuecomment-605749965 @ncmans the root cause is on third broker - `ledger=35 - operation=Failed to read entry - entry=0`. That means that your broker failed to read an entry when the bookkeeper cluster is being updated. I am guessing that the bookie stored `ledger 35` was being updated. I don't know how did you do a health check for your broker. I am guessing the health check in the helm chart wasn't implemented in the correct way, which causes K8S failed brokers when the bookie server is temporarily unavailable. You can reference our chart https://github.com/streamnative/charts to see how we implement the readiness and liveness probes: https://github.com/streamnative/charts/blob/master/charts/pulsar/templates/broker-statefulset.yaml#L135
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
