You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2022/05/04 23:35:23 UTC

[GitHub] [bookkeeper] dlg99 commented on issue #3150: How to recover Bookies that completely run out of storage space?

dlg99 commented on issue #3150:
URL: https://github.com/apache/bookkeeper/issues/3150#issuecomment-1118027134

   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 case.
   * Journal disk out of space: you can clean up older copies of journals, reduce journal file size to fit into the available space, reduce journalMaxBackups
   * ledger disks out of space: reduce logSizeLimit to fit two entrilogs into the available space (some other params may need to be adjusted too), maybe disable entryLogFilePreallocationEnabled
   
   I haven't tried this in awhile, I'd have to repro and spend more time than I have now to provide detailed instructions, so treat this as rough ideas.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@bookkeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org