[
https://issues.apache.org/jira/browse/HADOOP-9933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760380#comment-13760380
]
Karthik Kambatla commented on HADOOP-9933:
------------------------------------------
bq. what about just creating a new service instance on each startup, in the
existing process?
At least for now, we are planning to do this.
What do you think of the following?
Add a state PAUSED, (STARTED --> PAUSED), (PAUSED --> STARTED) are through
pause(), resume(). (PAUSED --> STOPPED) is also allowed. The Services can
decide what being PAUSED means, they could just shutdown their RPCServers or
clear their state completely.
If PAUSED is not the right word for it, we could move current STOPPED to
TERMINATED and add a state STOPPED. Current stop() will be terminate(). We can
add new methods stop() (STARTED --> STOPPED) and restart() (STOPPED -->
STARTED).
> 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
