[
https://issues.apache.org/jira/browse/HADOOP-9933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759162#comment-13759162
]
Karthik Kambatla commented on HADOOP-9933:
------------------------------------------
Thanks Steve. Agree with you that it is probably not the best idea to allow
restart for all services. I like your suggestion offline on restricting this to
RestartableService.
bq. Is there a way that we could avoid this
Initially, at least, I think it should be okay to create a new ActiveRMServices
instance (which holds all other RM services) everytime the RM transitions to
Active. In the longer term, I think it would be nicer to have restartable
versions of Service, AbstractService, and CompositeService.
Let me also think more about this. Any suggestions/thoughts will surely help.
> Augment Service model to support starting stopped services
> ----------------------------------------------------------
>
> Key: HADOOP-9933
> URL: https://issues.apache.org/jira/browse/HADOOP-9933
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.1.0-beta
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Labels: service
>
> For ResourceManager-HA (YARN-149 and co), we would want to start/stop/start
> RM's active services as it transitions to Active/Standby/Active respectively.
> In the current service model, we can't start the services that are already
> stopped.
> Would be nice to augment this. To avoid accidental restart of stopped
> services, we can add another API: start(boolean restartIfStopped). 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
