eolivelli commented on issue #2277: How to handle "not enough non-faulty Bookies" situation? URL: https://github.com/apache/bookkeeper/issues/2277#issuecomment-594532356 @RaulGracia IIUC your problem is about a Bookie that returns an error during a write due to server side throttling. In this case I am expecting an *ensembleChange* . I am trying to find in BK code the implementation of this behavior you are describing: ` However, the Bookkeeper Client is left in this state in which some of the Bookies are tagged as "faulty".` But I can't find it: the **EnsemblePlacementPolicy** is not notified about write errors, it only knows about Bookies that are no more available just by means of ZooKeeper Metadata Service Maybe you can take a look to the 'disableEnsembleChangeFeature': this feature may help in post poning the ensemble change and keep trying to use the temporary failed bookie (I have never used this feature)
---------------------------------------------------------------- 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
