[ https://issues.apache.org/jira/browse/BOOKKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277601#comment-13277601 ]
Rakesh R commented on BOOKKEEPER-237: ------------------------------------- @Flavio @Ivan +Handle multiple crashes:+ Soln-1: Each bookie will be looking to all and will act if my peer failed otw ignore, here it will have herd effect(everyone receives a notification). Soln-2: Central node will see the failures and notify the peer bookie. I feel Soln-2 is better and is used in 'Auto Recovery Detection - distributed chain approach.doc' > 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