[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527668#comment-13527668
]
Uma Maheswara Rao G commented on BOOKKEEPER-126:
------------------------------------------------
JIRA description:
{quote}
but we should detect corruptions like this and rereplicate if necessary.
{quote}
Yes, on closing BK-237 completely and BK-199, this JIRA can be closed.
But, In BK-237, the actual sub task(BOOKKEEPER-293) to solve this problem is
not yet addressed :-).
So, I don't think we can close this as resolved/fixed/implemented now.
I am ok to close this JIRA as duplicate with them(199,293) as other they will
handle this functionality on closer.
> 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
