You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (Commented) (JIRA)" <ji...@apache.org> on 2012/03/29 16:12:30 UTC

[jira] [Commented] (BOOKKEEPER-166) Bookie will not recover its journal if the length prefix of an entry is truncated

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241254#comment-13241254 ] 

Sijie Guo commented on BOOKKEEPER-166:
--------------------------------------

yeah, the journal did preallocate disk space. I agreed. +1 for the patch.
                
> Bookie will not recover its journal if the length prefix of an entry is truncated
> ---------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-166
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-166
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-166.diff
>
>
> Entries in the bookie's journal are written in the format <len><entry>
> If the bookie crashes while writing the length part, then the bookie will not be able to recover the journal.
> An unlikely situation to happen as this is only 1 int, but an issue none the less.
> There is a testcase in BOOKKEEPER-165 which will trigger this when enabled (BookieJournalTest#testTruncatedInLenJournal).

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