[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438711#comment-13438711
]
Uma Maheswara Rao G commented on BOOKKEEPER-272:
------------------------------------------------
{quote}
There should be a main method in AutoRecoveryManager. I think
AutoRecoveryManager should be responsible for running recoveryworker as well.
Im not sure whether the node which runs auditor should run a recovery worker at
the same time. This is an open question.
{quote}
Oh, I was assuming that, every Recovery node will have (Auditor Participants +
RW ) services running. But one will actually win for doing auditor work. But RW
will do its job normally in all nodes. All other recovery node's auditor
participants will look for the next election to win the Real Auditing job.
I am not sure my assumption is same as others. Any other thoughts?
> 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
> 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
