[
https://issues.apache.org/jira/browse/BOOKKEEPER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-62:
---------------------------------
Attachment: BOOKKEEPER-62.diff
Patch is good. I've made a few small mods.
1. Test is now in bookie package, so EntryLogger methods do not need to be
public.
2. Added logger to test, removed call to System.out.println
3. Changed log message on bad entry to a warn.
> 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.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
