[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230053#comment-13230053
]
Ivan Kelly commented on BOOKKEEPER-126:
---------------------------------------
@Sijie
Do we kill the bookie though? I think if an many errors occurs on flushing, we
should take the bookie out of rotation, as it indicates a failing disk.
@Rakesh
Proposal-2 is interesting, but it would only run on read, by which time it
could be too late. I think Proposal-3 is something we need in any case, though
to start it wouldn't have to be a daemon, but a tool that an admin could run to
verify the filesystem is in order.
> 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
