[jira] [Updated] (BOOKKEEPER-174) Bookie can't start when replaying entries whose ledger were deleted and garbage collected.

["Sijie Guo (Updated) (JIRA)" <ji...@apache.org>]

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

Sijie Guo updated BOOKKEEPER-174:
---------------------------------

    Attachment: BOOKKEEPER-174.diff

attach a patch to fix this issue. the idea is when encountering NoLedgerException on replaying journals, we need to check whether the ledger is still existed or not. if the ledger has been removed, we just skip replaying the entry.
                
> Bookie can't start when replaying entries whose ledger were deleted and garbage collected.
> ------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-174
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-174
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.0.0
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-174.diff
>
>
> if a journal contains entries which the ledgers they belongs to has been deleted and garbage collected, replaying such journal would encounter NoSuchLedgerException. And the bookie can't start.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira