You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Uma Maheswara Rao G (JIRA)" <ji...@apache.org> on 2012/12/17 16:58:46 UTC

[jira] [Updated] (BOOKKEEPER-472) Provide an option to start Autorecovery along with Bookie Servers

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Uma Maheswara Rao G updated BOOKKEEPER-472:
-------------------------------------------

    Attachment: BOOKKEEPER-472.patch

Attached an initial patch!
                
> 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
>         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