[
https://issues.apache.org/jira/browse/BOOKKEEPER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159805#comment-13159805
]
Benjamin Reed commented on BOOKKEEPER-62:
-----------------------------------------
i don't think we want this. if there is an error with an entry, all subsequent
entries should be considered erroneous. the journal will be used to recover the
erroneous entry all all subsequent entries.
> Bookie can not start when encountering corrupted records
> --------------------------------------------------------
>
> Key: BOOKKEEPER-62
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-62
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Sijie Guo
> Assignee: Benjamin Reed
> Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: BOOKKEEPER-62.diff, BOOKKEEPER-62.diff,
> BOOKKEEPER-62.patch, BOOKKEEPER-62.patch
>
>
> bookie tries to extract ledger ids from entry loggers during starting up. if
> some records corrupted, an IOException is thrown out.
> in extractLedgersFromEntryLogs function:
> line 459:
> int rc = bc.read(buff, pos);
> if (rc != data.length) {
> throw new IOException("Short read for entryLog " +
> entryLogId + "@" + pos + "(" + rc + "!="
> + data.length + ")");
> }
--
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
