[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230917#comment-13230917
]
Rakesh R commented on BOOKKEEPER-126:
-------------------------------------
Thanks Sijie,Ivan for the suggestions:-)
I think, the journal IOException would immediately reaches to the client as an
addEntry failure, so the client would be able to act upon it.
IMO, Can we narrow down to cases where IOException occurs on flushing ledger
entries and bookie is still running. Only those entries would select as
under-replicated, either an external tool can be triggered or shutdown the
bookie.
Also, I am bit confused when to shutdown the bookie, how to define the
threshold value for no: of IOExceptions. I feel, instead of shutdown the bookie
on IOException, shall we make use of ZK metadata(the entry-bookie mappings) and
identify a way using ZK(watchers) to notify peer bookies which has a replica of
that entry (build inter-bookie protocol through ZK).
> 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
