[ https://issues.apache.org/jira/browse/BOOKKEEPER-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048385#comment-16048385 ]
ASF GitHub Bot commented on BOOKKEEPER-1034: -------------------------------------------- Github user reddycharan commented on the issue: https://github.com/apache/bookkeeper/pull/190 @sijie this is the fix we are having to deal with bookie start when ledgerdirs are full. > When all disks are full, start Bookie in RO mode if RO mode is enabled > ----------------------------------------------------------------------- > > Key: BOOKKEEPER-1034 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1034 > Project: Bookkeeper > Issue Type: New Feature > Reporter: Charan Reddy Guttapalem > Assignee: Charan Reddy Guttapalem > Priority: Minor > > - When all disks are full start Bookie in RO mode if RO mode is enabled > - This will work only if "isForceGCAllowWhenNoSpace" is allowed, since > LedgerDirsManager.getWritableLedgerDirsForNewLog will be able to find new > writableLedgerDir even when all disks are full. > - If bookie has died abruptly then it may have missed flushing EntryMemtable > and > IndexInMemoryPageManager. So next time when it starts when disc is full > it fails to create index file and it shuts down. So Bookie should be able to > create index file though it has reached the diskusagethreshold, while > starting the Bookie in Readonly Mode. But ofcourse there should be some > config to safeguard when disk usable space is so low. -- This message was sent by Atlassian JIRA (v6.4.14#64029)