[
https://issues.apache.org/jira/browse/BOOKKEEPER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159389#comment-13159389
]
Ivan Kelly commented on BOOKKEEPER-62:
--------------------------------------
I spoke to Ben about this just now. The problem of short reads possibly
occurring due to corruption is another problem, which will need to be dealt
with in another way. We threw around a few ideas, like putting a bookie
internal txn id on each update each, which would allow us to detail gaps etc,
but nothing concrete. It is something we should fix for 4.1. For the moment,
the bookie system as a whole should detect if a bookie is missing entries and
read from another replica.
+1 for this patch for now. Opening another jira for the other issue.
> 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
>
>
> 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
