[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233327#comment-13233327
]
Rakesh R commented on BOOKKEEPER-126:
-------------------------------------
Yeah. when writing, bookkeeper client not choose the r/o bookie irrespective of
ledger and journal directories are in same or diff disk would be more feasible
to me.
@Sijie
flushing failure will not cause any entry under-replicated. (journal replay
will recover it). The case we need consider is that entries before lastLogMark.
If corruption happened on these entries, they are under-replicated.
Regarding this point: corruption due to disk failure will be a corner case, but
I feel it would be good to consider this also as bookkeeper is intended for
very sensitive metadata (either in this jira or a separate jira task). Here it
might required to have a periodic scanners and should handle under-replicated
blocks.
> 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
