[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527513#comment-13527513
]
Flavio Junqueira commented on BOOKKEEPER-126:
---------------------------------------------
Hi Rakesh,
Thanks for chiming in. My questions comes mostly from the fact that this jira
is marked as a blocker for 4.2.0, and we are trying to cut a release.
It sounds fine to incorporate other mechanisms that allow us to recover more
efficiently from various faults, but I'm not sure we should have them for
4.2.0. Is it ok if we have those for 4.3.0 or do you think they are blockers
for 4.2.0? In the case that we move this new functionality to 4.3.0, it would
be great to create new jiras or update existing jira to reflect it.
> 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.2.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
For more information on JIRA, see: http://www.atlassian.com/software/jira
