[
https://issues.apache.org/jira/browse/BOOKKEEPER-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-472:
----------------------------------
Fix Version/s: 4.2.0
> Provide an option to start Autorecovery along with Bookie Servers
> -----------------------------------------------------------------
>
> Key: BOOKKEEPER-472
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-472
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-472.patch
>
>
> We can also have an option to start the Autorecovery along with Bookie
> servers.
> If some users are not having too much load on the servers, they can even
> start them along the Bookie servers. If they feel, Auditor would disturb
> Bookie performance, they can anyway start as separate process.
> In another case, deployment overhead will reduce a bit as Monitoring process
> need not monitor one more process in their lifcycles etc.
> Thoughts?
--
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
