[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved BOOKKEEPER-1034.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.5.0

Issue resolved by merging pull request 190
            [https://github.com/apache/bookkeeper/pull/190]

            {noformat}
            commit 9ddd9e6f9e48b03a57a2c78ec2630303abd49782
Author:     Charan Reddy Guttapalem <cguttapa...@salesforce.com>
AuthorDate: Wed Jun 28 14:24:05 2017 -0700
Commit:     Sijie Guo <si...@apache.org>
CommitDate: Wed Jun 28 14:24:05 2017 -0700

    BOOKKEEPER-1034: Bookie start in RO when diskfull
    
    When the disk is above threshold, Bookie goes to RO. If we have to restart 
the
    bookie, on the way back, bookie tries to create new entrylog and other 
files,
    which will fail because disk usage is above threshold,
    hence bookie refuses to come up. So with this fix we will try to start in RO
    mode if RO is enabled.
    
    Also, if bookie has died abruptly then it may missed flushing EntryMemtable 
and
    IndexInMemoryPageManager. So next time when it starts when disc is full
    it is failing to create index file and it is shutting down, though we 
expect it
    to start in readonlymode. 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.
    
    Minor fixes in shutdown logic of Bookie and Bookieserver.
    
    Author: Charan Reddy Guttapalem <cguttapa...@salesforce.com>
    
    Reviewers: Jia Zhai <None>, Sijie Guo <si...@apache.org>
    
    This closes #190 from reddycharan/bookiestartinreadonlywhendiskfull

            {noformat}
            

> 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
>             Fix For: 4.5.0
>
>
> - 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)

Reply via email to