[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534644#comment-13534644
 ] 

Uma Maheswara Rao G commented on BOOKKEEPER-472:
------------------------------------------------

Thanks a lot, Ivan for taking a look.
Actually my intention here is to keep them in same JVM. Right now I may not 
encourage to run them in same jvm, mey be due to stability issues as you 
mentioned. But we are interested to run them as single process once 
autorecovery stabilized in future, otherwise OM need to monitor 2 processes 
instead of 1. So, this is currently just an optional and not documented yet.
Also our initial version of autorecovery is running along with Bookie process 
itself and going good. Also deployment perspective in NN HA is:
 2 NN, 2 ZKFC, 3 ZKs, 3 BKs + ( 3 Autorecovery processes) = 13 processes 
required to have NN HA.
This is just an optional, if we wanted to run them separately also we have that 
option as default.

                
> 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

Reply via email to