[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440211#comment-13440211
]
Rakesh R commented on BOOKKEEPER-272:
-------------------------------------
Thanks Ivan. I'll do the changes by just return if it matches as you suggested.
I'll investigate it later.
bq.Auditor will be a top level daemon, so it should own its create it's own
LedgerManagers and ZooKeeper client. The only thing passed in to is should be
the configuration.
Anyway we are planning to have initialization class which does starting Auditor
and RW threads. Would you agree to create ledgerManagers there and pass it to
the Auditor and RW daemons?
In that case, shall I keep the ctor as it is. (by taking managers)
{code}
public Auditor(String bookieIdentifier, AbstractConfiguration conf,
ZooKeeper zkc, LedgerManager ledgerManager,
LedgerUnderreplicationManager ledgerUnderreplicationManager) {
{code}
> 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-auto-recovery
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-272.1.patch, BOOKKEEPER-272.2.patch,
> BOOKKEEPER-272.3.patch, BOOKKEEPER-272.Auditor.1.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
