Il gio 15 feb 2018, 18:45 Ivan Kelly <iv...@apache.org> ha scritto: > Hi Bobby, > > One thing that should circumvent this is that the bookie should go > into readonly mode when it hits 95% full disk. > > This change is in your branch[1]. Have you disabled it? > > Regards, > Ivan > > [1] > https://github.com/yahoo/bookkeeper/blob/7fb556fa2dbc1d308b5d7ec3e2676b8b11704698/bookkeeper-server/conf/bk_server.conf#L247 > > On Thu, Feb 15, 2018 at 6:19 PM, Bobby Evans <ev...@oath.com.invalid> > wrote: > > We recently had a situation where the disk a journal is on filled up and > we > > ended up with a partial edit in the journal. This ended up being a > > METAENTRY_ID_LEDGER_KEY so only a partial master key was output and this > > ended up making the bookie fail on startup. > > > > Because we are running a forked version of bookkeeper I was wondering if > > anyone had done something to fix this in the past. If not I am happy to > > take a crack at it, but I don't want to double up efforts if it is > already > > fixed. > > > > Thanks, > > > > Bobby >
Nothing by my side, sorry. I know that sometimes some bookie crashed due to lack of disk space but my collegues simply dropped the bookie. Now that bookies turn into read-only mode the problems is mitigated a lot. Sorry Enrico > -- -- Enrico Olivelli
