[
https://issues.apache.org/jira/browse/BOOKKEEPER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399247#comment-13399247
]
Rakesh R commented on BOOKKEEPER-304:
-------------------------------------
Thanks Ivan, Flavio, Uma for your reviews and suggestions.
@Ivan
{quote}
My understanding of it is that the auditor will run in the bookie process but
will not directly access any bookie internals. Instead it will do everything
through the client API. The reason for putting it in the same process it just
that it's more convenient. It could be moved to a different process if this
proves problematic.
{quote}
ok. I think I got it. As part of this jira I'll prepare the bookie-ledger
indexing logic using LedgerManager interface and will keep as an independent
module.
Few more clarifications:
# But the bookkeeper-server would have to start the auditing service, still
this dependency has to be resolved?
# Also would like to know the suggestions on package structure?
> Prepare bookie vs ledgers cache and will be used by the Auditor
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-304
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-304
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-304.1.patch
>
>
> This JIRA discusses how to build bookie -> ledgers cache and this will be
> used by the Auditor to publish the suspected ledgers of failed bookies.
--
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
