[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290274#comment-13290274
 ] 

Ivan Kelly edited comment on BOOKKEEPER-237 at 6/6/12 5:20 PM:
---------------------------------------------------------------

In fact, this scheme could be made 100% distributed, by having an Auditor on 
each bookie, and having that auditor only monitor the ledgers which it knows 
that bookie contains. What may be tricky here is avoiding having all bookies in 
an ensemble run a scan on a single ledger at the same time.
                
      was (Author: ikelly):
    In fact, this scheme could be made 100% distributed, but having an Auditor 
on each bookie, and having that auditor only monitor the ledgers which it knows 
that bookie contains. What may be tricky here is avoiding having all bookies in 
an ensemble run a scan on a single ledger at the same time.
                  
> 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

        

Reply via email to