[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527422#comment-13527422
]
Rakesh R commented on BOOKKEEPER-126:
-------------------------------------
Hi Flavio,
I'd like to add few more and hope the following will help us to give more
clarity/conclusion.
This JIRA has helped us to initiate discussion and covered the following cases:
1) ledger entry failures during flushing/addEntry as part of BOOKKEEPER-199.
2) bookie failures will initiate re-replication and will be recovered the
ledger entries by autorecovery process BOOKKEEPER-237.
There could be an area of improvement for handling "disk failures"(this is also
another kind of data corruption). Say we have few closed ledgers which is
present in disk1 and this disk got failed. Presently if this happens admin has
option to shutdown the bookie and inturn autorecovery would start
re-replication. But can we think of an improvement of (bookie)self disk
scanning and a healing mechanism.
Whats your opinion?
-Rakesh
> 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
