andrekramer1 commented on issue #6603: URL: https://github.com/apache/pulsar/issues/6603#issuecomment-679013749
We've seen this error as well. A bookie appears to be unavailable as we get the "not enough bookies" error. The broker logs show a timeout for a bookie on one node while another node has a null reference exception while resolving in the logs. It's not clear if the bookie is actually up or marked unavailable by brokers in some way. Adding another bookie caused enough to be available again. There should be no NullReferenceExceptions reported. And any help with debugging failed bookies (as viewed by brokers) would be appreciated. Bookkeeper shell and Zookeeper seemed to list all bookies as available so the view as held by brokers is what's needed. ---------------------------------------------------------------- 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]
