[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294398#comment-13294398
]
Rakesh R commented on BOOKKEEPER-272:
-------------------------------------
Hi,
As part of this Auditor logic, I'm planning to publish the
suspected/underreplicated ledger metatdata as Ledger_BookieIP:PORT:
Assume we have three bookies BK1, BK2, BK3 and has ledgers L0001, L0002, L0003
Example:
Say, BK1 BK2 has failed and started two new bookies, then Auditor will be
publishing as:
/ledgers/auditor/underreplicated/L0001_BK1
/ledgers/auditor/underreplicated/L0002_BK1
/ledgers/auditor/underreplicated/L0003_BK1
/ledgers/auditor/underreplicated/L0001_BK2
/ledgers/auditor/underreplicated/L0002_BK2
/ledgers/auditor/underreplicated/L0003_BK2
By this, I'm thinking the target re-replicators would be able to acquire
distributed lock on L0001_BK1...etc and start re-replicating. Is this ok for
you?
Thanks,
Rakesh
> Provide automatic mechanism to know bookie failures
> ---------------------------------------------------
>
> 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.Auditor.patch
>
>
> The idea is to build automatic mechanism to find out the bookie failures.
> Setup the bookie failure notifications to start the re-replication process.
> There are multiple approaches to findout bookie failures. Please refer the
> documents 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
