[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242264#comment-13242264
]
Rakesh R commented on BOOKKEEPER-126:
-------------------------------------
Oh, I think I understood, for the corrupted/missing entries, the bookie should
read from the brother bookie and tries a write operation to himself(no ensemble
change req).
One corner case, if this re-write operation is failed in all the ledger dirs?,
probably forced to choose another bookie and form a new ensemble?
Secondly, for an opened/in-recovery ledger, how about the idea to check all the
brothers and if no read success corresponding to x entry, will consider (x - 1)
as the last entry. Packets in flight will be considered in the next pass, is it
ok?
> EntryLogger doesn't detect when one of it's logfiles is corrupt
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-126
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-126
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Priority: Blocker
> Fix For: 4.1.0
>
>
> If an entry log is corrupt, the bookie will ignore any entries past the
> corruption. Quorum writes stops this being a problem at the moment, but we
> should detect corruptions like this and rereplicate if necessary.
--
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
