[
https://issues.apache.org/jira/browse/BOOKKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242133#comment-13242133
]
Sijie Guo commented on BOOKKEEPER-126:
--------------------------------------
thanks, Rakesh.
+1 for opening a new jira discussion r-o mode when IOE flushing journal/ledgers.
{quote}
b) Read the entries and identify missing entries if any?
Yeah, the DistributionScheduling is happening in the client side and batch
reading is also good.
I am thinking that the ledgers are local to the server and how about read them
directly instead of using PerChannelBookieClient?.
{quote}
oh, seems that I don't explain clearly at my previous comment. As my thought,
bookie server would just find the corrupted/missing entries that it should own,
then schedule a re-replication procedure itself to read the corrupted/missing
entries from its brother bookie servers (in same quorum). so the read is a
remote read from other server.
in this way, we don't even to change the metdata in zookeeper.
as the example you explain,
{quote}
Say, entries 0-100 ledger metadata mapping is
0 (A, B, C)
50(B, C, D)
End Ledger:100
{quote}
B runs a scanner itself, it found that 30-39 is corrupted/missing. it schedule
a re-replication on (30-39), the re-replication would be a remote read (30-39)
from C or D. we don't need to change ledger metdata, changing ledger metdata
will introduce distribute consensus issue (you can refer discussion in
BOOKKEEPER-112).
{quote}
@Sijie
another tough thing is we need to tell closed ledger from opened/in-recovery
ledger, when handling last ensemble of opened/in-recovery ledger.
I am missing something, Could you give more details on this?
{quote}
for a closed ledger, we know the entry range of an ensemble. but for an
opened/in-recovery ledger, we have no idea about the end entry of last ensemble.
> 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
