[
https://issues.apache.org/jira/browse/BOOKKEEPER-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443074#comment-13443074
]
Vinay commented on BOOKKEEPER-319:
----------------------------------
Hi All,
I want to take up this Jira.
I assume the following from various discussions under BOOKKEEPER-237.
# Auditor will be a separate daemon, which also contains ReplicationWorker,
which should be started in all bookie machines.
# One of them will be elected as Auditor and start publishing the bookie
failures and under-replicated ledgers. Replication workers start replicating to
local bookie.
So here are my thoughts about current Jira,
# Create a class do start Auditor service and replication worker. How about
having class name as "AuditorPeer", similar to zookeeper "QuorumPeer"..?
# Include this in the bookkeeper scripts.
# Assuming that this daemon will be started from the same installation and
configurations as of bookie.
Any thoughts, suggestions, inputs are welcome.
Thanks.
> Manage auditing and replication processes
> -----------------------------------------
>
> Key: BOOKKEEPER-319
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-319
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Rakesh R
>
> This subtask discusses, how we will manage the whole rereplication processes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
