[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229130#comment-13229130
]
Ivan Kelly commented on BOOKKEEPER-126:
---------------------------------------
I haven't seen this issue occur in the wild, but it's something we've reasoned
is possible. So imagine that a logfile becomes corrupt, be it truncation or
full of junk. When the bookie tries to read an entry from the bookie which was
contained within the corrupted section, it will fail as if that entry did not
exist. This is safe within the system, because the entry will be read from
another bookie. However, we've lost a replica, so the data is underreplicated
and we don't know it. For this reason, each bookie should run some sort of fsck
process at an interval to ensure that everything is replicated sufficiently.
> 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
