[
https://issues.apache.org/jira/browse/BOOKKEEPER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400522#comment-13400522
]
Flavio Junqueira edited comment on BOOKKEEPER-272 at 6/25/12 3:17 PM:
----------------------------------------------------------------------
{quote}
bq. For the moment, and maybe for ever, whether the auditor runs should be
configurable
I haven't included in this patch, since there is still confusions whether to
treat as a plugin service or not.
{quote}
I think that whether the auditor runs or not should be configurable. Is that a
problem?
was (Author: fpj):
{quote}
{quote}
For the moment, and maybe for ever, whether the auditor runs should be
configurable
{quote}
I haven't included in this patch, since there is still confusions whether to
treat as a plugin service or not.
{quote}
I think that whether the auditor runs or not should be configurable. Is that a
problem?
> 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.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
