Andrey Yegorov

@hangc0276 @merlimat please take a look

I think this will fix the issue: https://github.com/apache/bookkeeper/pull/3350 I encountered this in the logs of the customer's cluster.

can you predictably repro the problem? Maybe my fix was not good enough :( but I only could repro it under docker with limited number of CPUs and after the...

`bin/bookkeeper shell readlog` reads specific local entry log file there is also `bin/bookkeeper shell localconsistencycheck` (Ithink bookie should be shut down for this one). Also check the disk for errors.

I have rather generic comments. > If the bookie cluster has remained bookies which place to /region/rack1, the ledger recovers to the /region/rack1 bookie again. As I understand, there is...

Also: https://github.com/apache/bookkeeper/pull/3359

hard to say without looking at `.../bookkeeper-server/hs_err_pid8605.log` but there is a chance this one is the same as https://github.com/apache/bookkeeper/issues/3040 @nicoloboschi is it possible to pick up logs like `hs_err_pid.*\.log` (if...

@1559924775 I hope you are still interested in fixing this issue. My PR https://github.com/apache/bookkeeper/pull/3023 fixes similar problem with routing of requests to threads, I think the routing logic change can...

Assuming you cannot add a new disk/expand existing disk: * can the bookie start as readonly? (forceReadOnlyBookie = true) I hope it won't try to create a journal in this...

I think the wait is related to https://github.com/apache/bookkeeper/blob/eadbdd4b6bfeef9924a3ff2c59fc3718cf3dc06b/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BookKeeperAdmin.java#L1623 You can make this time configurable via the decommission command flag / add logging.