[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290837#comment-13290837
]
Rakesh R commented on BOOKKEEPER-272:
-------------------------------------
??Why BKLedgerMapping :?? Parsing of ledgers and identifying failed bookies may
take long time, consider the case where lakhs of ledgers created by NN-HA edit
logs. So I thought of having a reverse mapping(bk vs its ledgers). Since this
mapping is constant until any re-replication, so I made it as persistent node
under 'bookieid'.
??Why Auditor :?? Single instance for entire bk cluster. After analyzing
multiple approaches I found this would avoid many problems, like few cases I
mentioned earlier in this JIRA.Please see links:
https://issues.apache.org/jira/browse/BOOKKEEPER-272?focusedCommentId=13284884&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13284884
> Introduce chain of bookies for distributing the re-replication
> --------------------------------------------------------------
>
> Key: BOOKKEEPER-272
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-272
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: BOOKKEEPER-272.1.patch, BOOKKEEPER-272.2.patch,
> BOOKKEEPER-272.patch
>
>
> The idea is to form logical chain and each Bookie will be taking care each
> other. On any Bookie failure, his neighbour will act and initiate
> re-replication.
> For example:
> Assume we have 1,2,3,4,5,6 bookies and will be forming the following chain
> 01 <- 02 <- 03 <- 04 <- 05 <- 06 <- 01
> Here, each one should take care of my immediate predecessor node. The lowest
> node should always care the highest node and is forming the logical closed
> chain.
> Reference docs attached in BookKeeper-237.
--
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
