[
https://issues.apache.org/jira/browse/BOOKKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291054#comment-13291054
]
Flavio Junqueira commented on BOOKKEEPER-237:
---------------------------------------------
It sounds we are not agreeing on terminology. A ledger fragment is the sequence
of entries an individual bookie stores for a given ledger. Say we have a e3-q2
ledger. If the writer writes entries A, B, C, we have the following fragments:
- For bookie 1: A, C
- For bookie 2: A, B
- For bookie 3: B, C
This is the terminology we have been using from the beginning. If there is any
documentation that could be misleading, it would be good to fix. Now, I don't
think we have agreed upon terminology to refer to the segment of a ledger
mapping to a given ensemble. I personally have been calling it an ensemble view
to refer to the ensemble composition and the ledger segment. Views is
terminology borrowed from distributed computing work on virtual synchrony and
group communication. The concept here is comparable.
> Automatic recovery of under-replicated ledgers and its entries
> --------------------------------------------------------------
>
> Key: BOOKKEEPER-237
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-237
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-client, bookkeeper-server
> Affects Versions: 4.0.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: Auto Recovery Detection - distributed chain
> approach.doc, Auto Recovery and Bookie sync-ups.pdf
>
>
> As per the current design of BookKeeper, if one of the BookKeeper server
> dies, there is no automatic mechanism to identify and recover the under
> replicated ledgers and its corresponding entries. This would lead to losing
> the successfully written entries, which will be a critical problem in
> sensitive systems. This document is trying to describe few proposals to
> overcome these limitations.
--
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
